← ClaudeAtlas

agent-config-auditlisted

Audit and sync AI agent configuration files (CLAUDE.md, CODEX.md, AGENTS.md, .cursorrules, hooks, settings) across workspaces. Use when agent configs drift, rules duplicate, files go stale, or after workspace restructuring.
shipshitdev/skills · ★ 27 · AI & Automation · score 72
Install: claude install-skill shipshitdev/skills
# 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. ## Contract Inputs: - Workspace root - Scope: full, dedup, stale, codex, cursor, settings, or fix - Optional list of repos/config files to include Outputs: - Audit report with critical/moderate/minor findings - Proposed fix plan - Applied changes only when fix mode is explicit Creates/Modifies: - Report mode: no file changes - Fix mode: agent config files, `.agents/` docs, and related settings External Side Effects: - None by default - Does not push, publish, or call external APIs Confirmation Required: - Before applying fix mode - Before overwriting existing agent configs - Before deleting or consolidating duplicated rules Delegates To: - `rules-capture` for single new preferences - `agent-folder-init` for missing `.agents/` structure - `session-documenter` when audit findings should be recorded ## 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 applicat