Module Regression Ledger
Track downstream consumers in REGRESSION.md and run affected commands after a change.
Install
npx skills add affaan-m/ECC --skill module-regression -g -a claude-code -y- Repository
- affaan-m/ECC295k
- Category
- Testing
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,892 tokens
- Runs scripts
- No, instructions only
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.
Module Regression Ledger
When to Activate
- The repository has at least three interdependent modules, or a previous change to A has broken B.
- A change modifies a module's externally observable behavior and must prove both that module and downstream consumers still work.
- The project already has executable tests or reconciliation commands that should be organized by dependency.
Anti-Patterns
- Creating a regression ledger for a small repository with no cross-module dependencies.
- Guessing dependencies manually or treating one scan as permanent truth.
- Replacing executable acceptance-command exit codes with model review.
Related Skills
test-collaboration: TEST-IDs, test assets, and defect-regression evidence.ai-regression-testing: executable regression tests derived from important defects.contract-first: cross-service or cross-client contract verification.change-impact: pre- and post-implementation blast-radius analysis.
Problem
In large projects, modules depend on one another. People and agents often verify only the changed module while downstream consumers fail silently. The defect appears days later when an aggregate, export, or external behavior is wrong.
The remedy is a regression ledger (REGRESSION.md) plus a deterministic audit: after any relevant change, run the changed module and all affected downstream consumers. Delivery requires every command to pass.
Three Required Fields per Module
## Module 03, Shop Data Cleaning
Downstream consumers: 05-aggregation, 07-final-export
Dependency evidence: `<repository dependency graph or reproducible scan command>`
Regression acceptance command: `pytest tests/test_03.py && python scripts/reconcile.py --module 03`
Propagation rule: external behavior change → run 05 and 07; internal-only change with a green module check → downstream may be exempted
