4f1cc7e0b7
New read-only command that shows everything Claude Code actually loads for a given repo — plugins, skills, MCP servers, hooks, CLAUDE.md cascade — with source attribution (user/project/plugin) and rough token estimates. Helps identify candidates for disabling without guessing. Added: - scanners/lib/active-config-reader.mjs — pure async helper: readActiveConfig, detectGitRoot, walkClaudeMdCascade, readClaudeJsonProjectSlice (longest-prefix matching for .claude.json projects), enumeratePlugins, enumerateSkills, readActiveHooks, readActiveMcpServers, estimateTokens (markdown 4 c/tok, json 3.5 c/tok, frontmatter cap 150 tokens, item flat 15) - scanners/whats-active.mjs — thin CLI shim: --json, --output-file, --verbose, --suggest-disables - commands/whats-active.md — renders tables via Read tool; honors UX rules - tests/lib/active-config-reader.test.mjs — 36 tests, all green (integration fixture built in tmpdir with fake HOME, .claude.json prefix matching, plugin discovery, hook/MCP merge from all scopes) Verified: - Performance budget: <2s wall-clock (smoke test: 102ms on real repo) - Token estimates within ±20% of hand-computed values - Read-only: no writeFile/mkdir/unlink in production code - Self-audit: Plugin Health scanner reports 0 findings (Grade A) - Full test suite: 522 tests, 512 pass (10 pre-existing conflict-detector failures on main — unrelated to this change, reproducible on clean HEAD) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.5 KiB
2.5 KiB
| name | description | allowed-tools | model |
|---|---|---|---|
| config-audit:help | Show all available config-audit commands | Read | sonnet |
Config-Audit: Help
Getting Started
Just run /config-audit — it auto-detects your project scope and runs a full audit. No setup needed.
All Commands
Core
| Command | Description |
|---|---|
/config-audit |
Full audit with auto-scope detection |
/config-audit posture |
Quick scorecard with A-F grades per area |
/config-audit feature-gap |
Deep analysis of features you're not using |
/config-audit fix |
Auto-fix deterministic issues with backup |
/config-audit rollback |
Restore configuration from a backup |
Planning & Implementation
| Command | Description |
|---|---|
/config-audit plan |
Generate prioritized action plan from audit findings |
/config-audit implement |
Execute action plan with automatic backup + verification |
/config-audit interview |
Set preferences to customize the action plan (optional) |
Monitoring
| Command | Description |
|---|---|
/config-audit drift |
Compare current config against a saved baseline |
/config-audit plugin-health |
Audit plugin structure and frontmatter quality |
/config-audit whats-active |
Show active plugins/skills/MCP/hooks/CLAUDE.md with token estimates |
Utility
| Command | Description |
|---|---|
/config-audit status |
Show current session state and progress |
/config-audit cleanup |
Clean up old session directories |
Advanced (workflow phases)
| Command | Description |
|---|---|
/config-audit discover |
Run only the discovery phase (find config files) |
/config-audit analyze |
Run only the analysis phase (generate report) |
Scope Override
By default, /config-audit auto-detects scope from your current directory:
- Inside a git repo → scans the repo
- In
$HOME→ scans global config only - Elsewhere → scans current directory
Override with: /config-audit current, /config-audit repo, /config-audit home, /config-audit full
Typical Workflows
First time? Just run /config-audit.
Want to fix things? Run /config-audit then /config-audit fix.
Full optimization:
/config-audit— see what you have/config-audit plan— create action plan/config-audit implement— execute with backups
Track changes over time:
/config-audit drift --save— save baseline- (make changes)
/config-audit drift— see what changed