doc-review
Skill181 starsChanged 9 months agoMITView on GitHub
Reviews and cleans up outdated documentation. Use periodically to maintain documentation health. Triggers on: review docs, clean up documentation, check for stale docs.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- momentmaker/kaijutsutheir own version, first seen Nov 1, 2026
- mbaneshi/claude-code-masterytheir own version, first seen Oct 20, 2026
- rterakedis/leanwheel-skillstheir own version, first seen Oct 17, 2026
- maaferna/job-search-agent-systemtheir own version, first seen Oct 15, 2026
- by-carlos/daikenjatheir own version, first seen Oct 13, 2026
- sd0xdev/sd0x-dev-flowtheir own version, first seen Oct 8, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- stacklok/toolhive★ 2.3ksame name
- ffroliva/gflow-cli★ 367same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- tlzmw001/aitest-kit★ 13same name
- ichangting/taotao-skills★ 8same name
- momentmaker/kaijutsu★ 3same name
- clearsmog/claude-skills★ 2same name
- rterakedis/leanwheel-skills★ 2same name
- andrewclark88/skills★ 1same name
5 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectSkill
- god-consensusSkill
- god-interventionSkill
- god-memberSkill
- observabilitySkill
- parallel-exploreSkill
- plan-reviewSkill
- prd-converterSkill
- prdSkill
- researchSkill
- roadmapSkill
- skill-creatorSkill
- vision-builderSkill
- visionSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Check for staleness indicators
- Distinctive: line 16
Verify referenced code/files still exist
- Distinctive: line 27
After each milestone completion
- Distinctive: line 33
When documentation feels outdated
- Distinctive: line 35
When onboarding reveals confusion
- Distinctive: line 155
Not modified in 60+ days
- Distinctive: line 158
No recent git commits mention the file
- Distinctive: line 172
Update file paths (if clear mapping exists)
- Distinctive: line 173
Remove broken external links
- Distinctive: line 174
Update version numbers in dependency lists
- Distinctive: line 283
Update docs with code: - When changing code, update related docs
“Common” is measured: kept by at least 6 in 10 of the 9 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
Doc Review Skill
Systematically review documentation for staleness, accuracy, and relevance.
The Job
- Scan all documentation files
- Check for staleness indicators
- Verify referenced code/files still exist
- Identify outdated content
- Generate cleanup report
- Optionally apply fixes
When to Use
Scheduled
- After each milestone completion
- Monthly maintenance cycle
- Before major releases
On Demand
- When documentation feels outdated
- After significant refactoring
- When onboarding reveals confusion
Review Process
Step 1: Inventory Documentation
Scan for documentation files:
find . -name "*.md" -not -path "./.git/*" -not -path "./.vendor/*" -not -path "./.worktrees/*"Common locations:
README.md(root and subdirs)docs/directoryAGENTS.md,CLAUDE.md.claude/skills/*/SKILL.mdknowledge/directoryscripts/aha-loop/templates/
Step 2: Check Staleness Indicators
For each document, check:
| Indicator | Check Method | Threshold |
| Last modified | git log -1 | > 30 days |
| Referenced files | grep + verify | Missing = stale |
| Code examples | Syntax check | Errors = stale |
| Version numbers | Compare to actual | Mismatch = stale |
| Links | HTTP check | Broken = stale |
Step 3: Verify Code References
For each code reference in docs:
## Code Reference Check
File: [doc-path]
Reference: `src/main.rs:45-60`
Status: [Exists | Missing | Changed]
If Changed:
- Original: [what doc says]
- Current: [what code shows]
- Action: [Update doc | Flag for review]Step 4: Check External Links
# Extract URLs
grep -oP 'https?://[^\s)]+' file.md
# Check each URL
curl -s -o /dev/null -w "%{http_code}" URLStep 5: Generate Report
Create docs-review-report.md:
# Documentation Review Report
**Date:** [YYYY-MM-DD]
**Reviewed:** [N] files
**Issues Found:** [N]
## Summary
| Category | Count |
|----------|-------|
| Stale (>30 days) | [N] |
| Missing References | [N] |
| Broken Links | [N] |
| Outdated Examples | [N] |
## Issues by File
### [file1.md]
- [ ] Line 45: Reference to `src/old.rs` - file no longer exists
- [ ] Line 78: Code example uses deprecated API
### [file2.md]
- [ ] Line 12: Version "1.0.0" should be "2.0.0"
- [ ] Line 56: Broken link to external docs
## Recommended Actions
1. **Delete:** [files that should be removed]
2. **Update:** [files that need content updates]
3. **Review:** [files that need human review]
## Auto-fixable
The following can be auto-fixed:
- [ ] Update version numbers
- [ ] Remove dead links
- [ ] Update file paths
Run `./scripts/aha-loop/doc-cleaner.sh --fix` to apply.Staleness Criteria
Definitely Stale
- References files that don't exist
- Contains code that doesn't compile
- Links to 404 pages
- Describes features that were removed
Probably Stale
- Not modified in 60+ days
- Uses old API patterns
- References old version numbers
- No recent git commits mention the file
Needs Human Review
- Contains outdated but complex content
- Describes deprecated but still-supported features
- Historical documentation (changelogs, decisions)
Auto-Fix Rules
Safe to Auto-Fix
- Update file paths (if clear mapping exists)
- Remove broken external links
- Update version numbers in dependency lists
- Fix obvious typos in code references
Requires Human Review
- Content changes beyond mechanical updates
- Removing entire sections
- Changing technical instructions
- Modifying architecture decisions
Integration
With Doc Cleaner Script
# Generate report only
./scripts/aha-loop/doc-cleaner.sh --report
# Apply safe fixes
./scripts/aha-loop/doc-cleaner.sh --fix
# Interactive mode
./scripts/aha-loop/doc-cleaner.sh --interactiveWith Observability
Log review activities:
## 2026-01-29 16:00:00 | Task: Maintenance | Phase: Doc Review
### Documentation Review
Scanned 45 files, found 7 issues.
### Key Findings
- AGENTS.md references outdated skill paths
- README example code uses deprecated API
### Actions Taken
- Auto-fixed 3 version number issues
- Flagged 4 items for human reviewChecklist
Before completing review:
- All markdown files scanned
- Code references verified
- External links checked
- Report generated
- Auto-fixes applied (if safe)
- Human review items flagged
Example Review
Input
File: docs/api.md last modified 90 days ago
# API Documentation
## Authentication
See `src/auth/mod.rs` for implementation.
Use version 0.5.0 of the auth library:
```toml
auth-lib = "0.5.0"More info: https://example.com/old-docs
### Review Findings
1. **Stale**: Last modified 90 days ago
2. **Missing Reference**: `src/auth/mod.rs` doesn't exist (moved to `src/api/auth.rs`)
3. **Outdated Version**: Current version is 1.2.0, not 0.5.0
4. **Broken Link**: https://example.com/old-docs returns 404
### Report Entry
```markdown
### docs/api.md
**Staleness:** 90 days since last update
**Issues:**
- [ ] Line 5: `src/auth/mod.rs` → `src/api/auth.rs`
- [ ] Line 8: Version 0.5.0 → 1.2.0
- [ ] Line 12: Broken link (404)
**Recommendation:** Update file paths and versions, remove broken linkPrevention
To reduce future staleness:
- Update docs with code - When changing code, update related docs
- Add doc checks to CI - Fail on broken references
- Schedule regular reviews - Monthly or per-milestone
- Use relative links - Easier to maintain than absolute
- Date-stamp examples - "As of v1.2.0"
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.

