← ClaudeAtlas

agent-config-auditlisted

Audit AI agent instruction files (AGENTS.override.md, AGENTS.md, configured fallbacks, CLAUDE.md, hooks, and settings) across workspaces in read-only report mode. Use when agent configs drift, rules duplicate, files go stale, or after workspace restructuring; apply fixes only when explicitly requested.
shipshitdev/skills · ★ 35 · AI & Automation · score 77
Install: claude install-skill shipshitdev/skills
# Agent Config Audit ## Contract Inputs: - Workspace root - Scope: full, dedup, stale, instructions, 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, but only after an explicit fix request and confirmation of the exact plan External Side Effects: - None by default - Does not push, publish, or call external APIs Confirmation Required: - Before entering fix mode or using any mutating file/shell operation; an audit or sync request alone authorizes report mode only - 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 ## 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 `bug` or `refactor-dispatch` - If