← ClaudeAtlas

ccc-claudemdlisted

Audit the project CLAUDE.md against the codebase — stale paths, dead commands, token waste — fixes applied only after AskUserQuestion approval. Use when: 'audit claude md', 'optimize instructions'.
KevinZai/commander · ★ 6 · AI & Automation · score 74
Install: claude install-skill KevinZai/commander
# $ccc-claudemd — CLAUDE.md Auditor Compares the project's CLAUDE.md instructions against the real state of the codebase and proposes concrete fixes. **Nothing is edited without explicit AskUserQuestion approval** — the permission ask is native to this flow. **CC Commander** · $ccc-claudemd · Keep your instructions honest > The ambient suggest engine recommends this skill when `claudeMdAgeDays > 30` (from the per-project state at `~/.claude/commander/projects/<slug>/project-state.json` — locate it with `ls -d ~/.claude/commander/projects/$(basename "$PWD")-*`; the flat pre-v7.3.0 path is no longer written). If the project has NO CLAUDE.md at all, route to `$ccc-adopt` instead — it owns the create flow (diff preview → approval → backup → delimited write). ## What It Checks ### 1. Stale References - File paths mentioned in CLAUDE.md that no longer exist - Commands referenced that aren't in package.json scripts (or Makefile/justfile targets) - Dependencies mentioned that aren't in package.json / pyproject.toml / Cargo.toml - Tool/framework references that don't match installed versions - Counts and version strings that drifted from reality (prove before alarm — verify each against the live tree before flagging) ### 2. Missing Context - Key directories not documented (src/, lib/, tests/) - Package.json scripts not mentioned - Environment variables used in code but not documented - MCP servers configured but not referenced - Git hooks or CI workflows not mentioned ### 3. Ca