audit-docs
Skill11 starsChanged 18 days agoMITView on GitHub
Audit documentation gaps by comparing code changes between the last docs update (or release version) and current HEAD. Detects undocumented features, modified tools/skills, configuration changes, and KO-EN translation parity drift. Use when checking for missing documentation, auditing doc gaps, verifying translation parity, or preparing documentation before releases. Triggers on: "audit docs", "audit-docs", "문서 누락 검토", "문서 누락 감사", "docs audit", "문서 드리프트 감사", "마지막 docs 업데이트 분석".
17 other projects use a version of this.
Adopted by
Most recently taken up by
- TserenTserenov/FMT-exocortex-templatetheir own version, first seen Nov 2, 2026
- iwesys/IWEtheir own version, first seen Nov 1, 2026
- driangle/vibeviewtheir own version, first seen Nov 1, 2026
- Evan-Daruwalla/claude-skill-suitetheir own version, first seen Oct 20, 2026
- LandonTomaine/LT-Agentstheir own version, first seen Oct 20, 2026
- faparicior/sdlc-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use diagnose.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilldiagnose
Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- opsmill/infrahub★ 548same name
- frankarobotics/franka_ros2★ 392same name
- chrisguidry/docket★ 148same name
- TserenTserenov/FMT-exocortex-template★ 63same name
- DGouron/review-flow★ 42same name
- gtrabanco/agentic-workflow★ 23same name
- driangle/vibeview★ 4same name
- bmaltais/skills★ 2same name
- faparicior/sdlc-skills★ 2same name
- krixon/skills★ 1same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- agents.mdAGENTS.md
- .agents/skills/react-best-practices/AGENTS.mdAGENTS.md
- .agents/skills/react-native-skills/AGENTS.mdAGENTS.md
- .agents/skills/react-view-transitions/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agent-initSkill
- agy-delegateSkill
- code-audit-expertSkill
- computer-diagnosisSkill
- create-builtin-toolSkill
- create-prSkill
- critique-builtin-toolSkill
- doc-auditorSkill
- docxSkill
- extract-log-debugSkill
- feature-refactor-proposalSkill
- gatekeeper-loopSkill
- harbor-harness-improvement-loopSkill
- i18n-language-standardsSkill
- jobs-trace-analyzerSkill
- lean-builtin-tool-auditorSkill
- libragent-qualitySkill
- libr-delegateSkill
- libr-tool-e2e-harness-loopSkill
- modular-large-file-refactorSkill
- performance-auditSkill
- pptxSkill
- vercel-react-best-practicesSkill
- vercel-react-native-skillsSkill
- vercel-react-view-transitionsSkill
- readme-showcase-syncSkill
- refactor-builtin-toolSkill
- release-managerSkill
- review-local-changesSkill
- review-pr-commentsSkill
- science-searchSkill
- setup-wizardSkill
- skill-creatorSkill
- soul-awakeningSkill
- sqlite-analyzerSkill
- sync-pending-approvalsSkill
- tool-creatorSkill
- trace-analyzerSkill
- trace-eval-loopSkill
- vitepress-doc-syncSkill
- worker-loopSkill
- x-cliSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Run the helper script to detect baseline commits, code changes, and doc parity:
- Very specific: line 82
Check the KO ↔ EN Documentation Parity Audit table from the script:
- Distinctive: line 93
When writing or reviewing English documentation, enforce ASD-STE100 principles:
- Very specific: line 101
Avoid ambiguous modals (should, might).
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Audit Docs Skill
Analyze the gap between the codebase changes (features, tools, skills, settings) made since the last documentation update (or release tag) and current HEAD. Verify whether user documentation (website/ and docs/user/) accurately reflects these changes and maintains Korean-English translation parity.
🧭 Workflow Decision Tree
1. Run Automated Audit Script
└─ python3 .agents/skills/audit-docs/scripts/audit_docs.py [--since <REF> | --release]
2. Inspect Code Changes vs Document Mapping
├─ Built-in Tools → docs/user/guides/builtin-tools.md
├─ Bundled Skills → docs/user/guides/skills.md
├─ Settings/Config → docs/user/guides/troubleshooting.md & getting-started/
└─ Scenarios/Workflows → docs/user/scenarios/
3. Audit KO ↔ EN Translation Parity & Truncation
└─ Check if EN ratio < 70% or headings mismatch
4. Verify ASD-STE100 Style Compliance
└─ Check active voice, imperative verbs, sentence length <= 20-25 words
5. Output Structured Audit Report & Action PlanStep 1: Run the Audit Script
Run the helper script to detect baseline commits, code changes, and doc parity:
# 1. Automatic mode: Compares against the last commit that touched docs/user/
python3 .agents/skills/audit-docs/scripts/audit_docs.py
# 2. Release mode: Compares against the latest Git release tag
python3 .agents/skills/audit-docs/scripts/audit_docs.py --release
# 3. Custom baseline: Compares against a specific branch or commit ref
python3 .agents/skills/audit-docs/scripts/audit_docs.py --since dev/0.9.x~10
# 4. JSON format for machine parsing
python3 .agents/skills/audit-docs/scripts/audit_docs.py --json --output audit_report.jsonStep 2: Analyze Code Diffs & Map to Docs
Inspect code diffs between baseline and HEAD across five key architectural domains:
| Code Domain | Source Paths | Target User Documentation |
| Bundled Skills | src-tauri/bundled_skills/ | docs/user/guides/skills.md |
| Built-in Tools | src-tauri/src/mcp/, src-tauri/src/agent/tools/ | docs/user/guides/builtin-tools.md |
| Settings & Config | src/components/settings/, src-tauri/src/config/ | docs/user/guides/troubleshooting.md, getting-started/connecting-models.md |
| UI Views / Routes | src/views/, src/routes/ | docs/user/guides/navigation-guide.md, docs/user/index.md |
| Automation / Cron | src-tauri/src/scheduled/ | docs/user/guides/scheduled-tasks.md, docs/user/guides/automation.md |
Verification Checklist:
- Were new skills added to
bundled_skillswithout being listed in the Skills Catalog? - Were new MCP tools or tool parameters added without reference entries?
- Were UI setting keys renamed or added without updating troubleshooting and setup guides?
- Were new execution modes (e.g.,
YOLO,Unsafe,Normal) added without documentation?
Step 3: Audit KO ↔ EN Translation Parity
A common pitfall is updating Korean documentation while leaving English documents as outdated skeletons.
Check the KO ↔ EN Documentation Parity Audit table from the script:
MISSING_EN: Korean document exists, but English counterpart does not exist. (Critical)SEVERE_TRUNCATION(Ratio < 40%): English document is severely abbreviated or a placeholder stub. (High)MODERATE_TRUNCATION(Ratio 40% ~ 70%): English document misses key tables, tips, or sections. (Medium)OK(Ratio >= 70%): Content volume and structural depth match.
Step 4: Verify ASD-STE100 Style Guidelines
When writing or reviewing English documentation, enforce ASD-STE100 principles:
- Sentence Length:
- Procedural instructions: <= 20 words.
- Descriptive statements: <= 25 words.
- Imperative Verbs:
- Begin instruction steps with active verbs (
Specify,Configure,Inspect,Run).
- Begin instruction steps with active verbs (
- Clarity and Precision:
- Avoid ambiguous modals (
should,might). Usemustfor requirements,canfor capabilities. - Restrict consecutive noun clusters to 3 words or fewer.
- Avoid ambiguous modals (
Step 5: Generate the Final Audit Report
Structure the final audit report using this markdown format:
# 📋 Documentation Gap Audit Report
## 1. Audit Scope & Baseline
- Baseline: `<COMMIT_HASH>` (<SUMMARY>)
- Target Head: `<HEAD_HASH>`
- Audit Mode: `<AUTOMATIC | RELEASE | CUSTOM>`
## 2. Code Changes vs. Document Mapping Gaps
| Change Type | Component / File | Detected Code Change | Affected Documentation | Status |
| ----------- | ---------------- | ----------------------- | ------------------------- | ----------- |
| New Skill | `skill-name` | Added to bundled_skills | `guides/skills.md` | 🔴 Missing |
| Tool Flag | `browser` | Added `--sandbox` arg | `guides/builtin-tools.md` | ⚠️ Outdated |
## 3. Translation Parity Findings (KO ↔ EN)
- Total Files Audited: XX
- Truncated / Outdated EN Files: X
- Parity Gaps List:
- `path/to/doc.md`: Ratio XX%, missing sections: [...]
## 4. Actionable Remediation Plan
1. [P0] Update `guides/skills.md` (KO & EN) to include `new-skill`.
2. [P1] Re-translate `path/to/doc.md` to ASD-STE100 standards.
3. [P2] Run `pnpm --filter libragent-docs build` to verify clean build.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

