module-regression
Maintains a REGRESSION.md ledger of module dependencies and executable acceptance commands so that changes to one module are verified against all downstream consumers before delivery.
What it does
Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected downstream command, and use observed exit codes as regression evidence under the project's delivery policy. Use for module regression, regression ledgers, impact audits, downstream verification, and changes where modifying A may break B.
Quality judgment
Comprehensive, well-structured skill with clear activation criteria, anti-patterns, invariants, boundaries with adjacent skills, and a detailed audit flow. Examples are present but limited to ledger formatting rather than end-to-end worked scenarios; otherwise near-excellent.