7b57b2e091
Before: SEO.md, GEO.md, HARDEN.md, VALIDATE.md, BUGS-FOUND.md landed
at project root. After: all five go to .claude/audits/. Covers both
dispatcher write paths and the dispatcher bash commands that parse
each report (test -s, grep score, wc) — otherwise the dispatcher
would look for the file at the old location.
- skills/seo,geo,harden,validate,code-clean — write paths + console
summaries ("Report: .claude/audits/X.md")
- skills/harden,validate — bash parsing commands (test/grep/wc) aligned
- agents/seo-analyzer,validator-analyzer,code-cleaner — agent-side refs
- agents/validator-analyzer frontmatter description updated
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
901 B
901 B
| name | description | argument-hint | disable-model-invocation | allowed-tools | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| code-clean | Full codebase cleanup: dead code removal, style/norm enforcement, structural issues. Two-phase workflow: audit first (read-only report), then execute approved fixes only. Delegates refactoring to the refactorer agent. Trigger: "code-clean", "clean up the code", "remove dead code", "enforce code style", "cleanup", "nettoyage du code", "code hygiene". For targeted refactoring without audit → use /refactor instead. For bug fixes discovered during cleanup → logged to .claude/audits/BUGS-FOUND.md, not fixed here. | <file, directory, or blank for entire project> | false |
|
Load and follow strictly:
- $HOME/.claude/agents/code-cleaner.md
Execute the CODE-CLEANER agent on the following target:
$ARGUMENTS