deep-auditlisted

# /deep-audit — Repository Infrastructure Audit Run a comprehensive consistency audit across the entire repository, fix all issues found, and loop until clean. ## When to Use - After broad changes (new skills, rules, hooks, scripts, AGENTS.md edits) - Before releases or major commits - When the user asks to "find inconsistencies", "audit", or "check everything" ## Workflow ### PHASE 1: Launch 4 Parallel Audit Agents Launch these 4 agents simultaneously using `Agent` with `subagent_type=general-purpose`: #### Agent 1: Canonical Docs Accuracy Focus: `AGENTS.md` (the single canonical description) and `README.md` (short external intro) - All numeric claims match reality (skill count, agent count, rule count, hook count, script count) - All file paths mentioned actually exist on disk - All skill/agent/rule/script names match actual directory and file names - Code examples and commands are correct (`scripts/deckpath.py`, `scripts/deckprofile.py`, `scripts/new_deck.py` flags exist) - Cross-references resolve - No stale counts, and no mentions of layers that git history shows as removed #### Agent 2: Hook Code Quality Focus: `.claude/hooks/*.py` and `.claude/hooks/*.sh` - No remaining `/tmp/` usage (should use `~/.claude/sessions/`) - Hash length consistency (`[:8]` across all hooks) - Proper error handling (fail-open pattern: top-level `try/except` with `sys.exit(0)`) - JSON input/output correctness (stdin for input, stdout/stderr for output) - Exit code correctness (0 for n