Agent Config Audit

Audit and maintain the full AI agent configuration stack across a workspace — CLAUDE.md, CODEX.md, AGENTS.md, .cursorrules, hooks, settings, and supporting .agents/ docs.

When to Use

• User mentions: "audit CLAUDE.md", "agent config", "rules out of date", "config drift", "sync docs"
• After restructuring repos, adding/removing projects, or changing conventions
• Periodic maintenance (monthly recommended)
• When agents keep making the same mistake despite rules existing (symptom of stale or contradictory config)
• After a major refactor where file paths, package names, or architecture changed

When NOT to Use

• If writing actual application code → use bugfix, refactor-code, or repo-specific skills
• If capturing a single new rule from conversation → use rules-capture
• If auditing code quality / CRITICAL-NEVER-DO violations → use genfeed-codebase-audit
• If checking formatter/linter configs (biome, prettier, tsconfig) → use genfeed-config-harmony
• If scaffolding .agents/ from scratch → use agent-folder-init