CLAUDE.md Improver
Audit, evaluate, and improve CLAUDE.md files across a codebase.
Workflow
Phase 1: Discovery
Find all CLAUDE.md files:
bash
find . -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" 2>/dev/null | head -50
File Types:
| Type | Location | Purpose |
|---|---|---|
| Project root | ./CLAUDE.md | Primary project context (shared with team) |
| Local overrides | ./.claude.local.md | Personal/local settings (gitignored) |
| Global defaults | ~/.claude/CLAUDE.md | User-wide defaults |
| Package-specific | ./packages/*/CLAUDE.md | Module-level context in monorepos |
Phase 2: Quality Assessment
| Criterion | Weight | Check |
|---|---|---|
| Commands/workflows documented | High | Build/test/deploy commands present? |
| Architecture clarity | High | Can Claude understand the codebase structure? |
| Non-obvious patterns | Medium | Gotchas and quirks documented? |
| Conciseness | Medium | No verbose or obvious info? |
| Currency | High | Reflects current codebase state? |
| Actionability | High | Instructions executable, not vague? |
Quality Scores:
- •A (90-100): Comprehensive, current, actionable
- •B (70-89): Good coverage, minor gaps
- •C (50-69): Basic info, missing key sections
- •D (30-49): Sparse or outdated
- •F (0-29): Missing or severely outdated
Phase 3: Report
Output quality report BEFORE making any updates.
Phase 4: Targeted Updates
After user approval:
- •Propose targeted additions only
- •Keep minimal - avoid restating what's obvious
- •Show diffs for each change
Phase 5: Apply
Apply changes using Edit tool. Preserve existing structure.
What Makes a Great CLAUDE.md
- •Concise and human-readable
- •Actionable commands that can be copy-pasted
- •Project-specific patterns, not generic advice
- •Non-obvious gotchas and warnings
- •Sections: Commands, Architecture, Key Files, Code Style, Environment, Testing, Gotchas