Audit Analyzer

Parse audit entries and update requirement tracking tables.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/doghelWang/amr_studio_v4 --skill audit-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Audit Analyzer
Source: https://github.com/doghelWang/amr_studio_v4/tree/main/skills/audit_analyzer
Command: npx skills add https://github.com/doghelWang/amr_studio_v4 --skill audit-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates converting manual audit notes into a structured requirement-tracking workflow, reducing manual coordination and ensuring traceability.

Core Features & Use Cases

  • Structured Audit Schema: Enforces a consistent format for each audit entry, including Date, Category, Description, Expected Result, Test Method, and Status.
  • Workflow Integration: Extracts the latest audit entries from docs/audit/人工检查.md and pushes updates to the requirement tracking table and task list.
  • Traceability & Verification: Ensures audit items link to persistent requirement IDs and supports verification steps in walkthrough.md.

Quick Start

Run the Audit Analyzer to parse the latest entries in docs/audit/人工检查.md and update the requirement tracking table.

Frequently Asked Questions about Audit Analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate parsing manual audit notes into a requirement tracking table?▼

Automating manual audit parsing extracts the latest entries from docs/audit/人工检查.md and directly updates the requirement tracking table and task list to enforce structured traceability without manual coordination.

What structured format should manual audit entries follow for automated requirements tracking?▼

A structured audit schema enforces a consistent format requiring Date, Category, Description, Expected Result, Test Method, and Status for each manual audit entry to ensure automated traceability.

How do I link audit entries to persistent requirement IDs for verification?▼

Linking audit entries to persistent requirement IDs is handled automatically during parsing, pushing updates from the manual audit log to requirement_tracking.md and supporting verification steps in walkthrough.md.

Can I use this workflow to update task lists alongside requirement tracking from audit logs?▼

Updating task lists alongside requirement tracking is fully supported, automatically pushing extracted audit entries to both task.md and requirement_tracking.md to provide an end-to-end workflow from extraction to verification.

What's the best way to maintain traceability across manual audit workflows?▼

Maintaining traceability across manual audit workflows is achieved by enforcing a structured audit schema and automatically linking extracted items to persistent requirement IDs within the tracking table.

Do I need any external dependencies to run the automated audit extraction and tracking workflow?▼

No external dependencies are required to run the automated audit extraction workflow, which directly reads from docs/audit/人工检查.md and writes updates to the application's local brain directory.