context-audit

Auditing CLAUDE.md context leakage involves tracing references from rules to knowledge leaves to identify orphaned files. This skill validates the three-layer progressive disclosure system and generates a structured compliance report with actionable remediation steps for stale knowledge.

Progressive disclosure compliance ensures all knowledge files are reachable from rules without orphaned files or index leakage. It validates end-to-end consistency across CLAUDE.md, rule definitions, and knowledge leaves to maintain reliable project context architecture.

Checking for stale references and orphaned files requires tracing rule-to-knowledge links within the context management system. The audit identifies deprecated knowledge, mislinked files, and gaps in rule coverage, then outputs remediation steps to restore hygiene.

Context auditing is designed specifically for the three-layer architecture of CLAUDE.md, rules, and knowledge. Without this progressive disclosure structure, the compliance checks for index leakage, orphaned files, and reference tracing cannot be properly validated.

Validating rule coverage and knowledge reachability is best done by tracing references from rules to knowledge leaves end-to-end. This detects unreachable knowledge files and CLAUDE.md index leakage, producing a structured compliance report with specific remediation actions.

Context audit reports show rule coverage gaps when knowledge files are orphaned, mislinked, or deprecated within the progressive disclosure system. The audit traces references from rules to knowledge leaves and flags these inconsistencies as actionable remediation steps.