What problem does it solve?
Individual validators each check one rule, so cross-cutting repository issues like orphaned family contracts, sample gaps, stale declared counters, and skills missing matching commands slip through undetected before a release.
Core Features & Use Cases
- Aggregated Validator Suite: Invokes the full enforcing validator bundle via
scripts/pre-tag-validate.sh and consolidates results into one report.
- Cross-Cutting Checks: Detects issues no single validator catches, such as dead skill references, sample gaps, and description collisions, graded P0 through P3.
- Counter Re-Derivation: Re-counts skills, commands, sub-agents, and workflows from the filesystem and compares them against values declared in CONTEXT.md, AGENTS.md, and README.md.
- Layered Output: Produces a full audit report, a prose Status Summary, and a machine-readable Status YAML block for downstream tooling like release gates.
- Use Case: Before tagging a release, run a full-scope audit with a P1 severity floor to confirm zero P0 findings and verify that declared catalog counts match the actual repository state.
Quick Start
Ask the AI to run a full pre-release governance audit of the repository with a P1 severity floor and return the findings report with the machine-readable status block.