claude-code-audit

# Claude Code Audit This skill does three jobs, in order: 1. **Stay current** — self-update the capabilities reference from the live docs (Step 0). 2. **Diagnose** — a liveness canary FIRST (catch silently-broken things and report how long each has been broken), then the full scan across the whole setup (Steps 0.5 to 3). The scan is self-discovering: it diffs the live system against the last run's inventory and probes anything new, so it does not go blind to things built since the checklist was written. 3. **Self-maintain** — auto-execute safe cleanup, batch the risky cleanup into one approval, surface secrets only (Steps 4-5). The point is that ONE manual trigger catches everything, including breakage that has been silent for days. The skill runs on demand; proactivity comes from the canary plus "broken since" surfacing, not from any background schedule (the operator triggers it). Safe cleanup happens by default; the user is asked only about changes that are risky, irreversible, or touch secrets. Reference files (read at the step that needs them, not up front): - `references/capabilities.md` — the Claude Code capability knowledge base (Step 0 maintains it). - `references/checklist.md` — the Step 0.5 liveness canary, the dynamic-discovery block, and the Step 2 diagnostic rubric. - `references/cleanup-tiers.md` — the Step 4 risk classification + auto-execute protocol. - The newest system-inventory document, if one is kept — a dated description of the whole setup, produced ...