What problem does it solve?
Review the staleness and usefulness of any agent-facing knowledge in the repo:
rule files (.claude/rules/), AGENTS.md (at any depth), CONVENTIONS.md, README.md,
and domain docs if present. Use this skill whenever the user wants to audit, clean
up, or prune their knowledge base: "audit rules", "audit docs", "audit knowledge",
"review rules for staleness", "clean up the rules", "are any docs outdated?",
"prune old knowledge", "check if rules are still relevant", "knowledge audit",
or any variation. Also trigger when the user says they're confused by a rule/doc
that seems wrong — use that as the starting point for a broader audit.
Core Features & Use Cases
Audit every agent-facing knowledge file in the repo for staleness, accuracy, and usefulness. Stale knowledge is worse than no knowledge — it sends sessions in the wrong direction. Knowledge files include:
.claude/rules/*.md — auto-injected rules
AGENTS.md at any depth (root and per-package)
CONVENTIONS.md — code-style source of truth
README.md — human-facing but agents read it too
docs/domain/*.md if the repo uses that pattern
Quick Start
Run the knowledge-audit skill to scan and report on all agent-facing knowledge files, with optional scope modifiers for rules, docs, or specific AGENTS.md entries.