Agent skill · affaan-m
module-regression
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.
What it needs
About 5k tokens when loaded.
What this skill does
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 1. Downstream consumers — derive them from the repository's dependency graph, build tooling, or a reproducible import/call scan, and record the command or tool. Extraction differs by ecosystem; this skill does not pretend a universal scanner can parse every language. Mark edges unverified when they cannot be established mechanically. An affected unverified edge blocks an all-green verdict until a human confirms its scope or the related module is included in the run. 2. Regression acceptance command — the ledger's core asset. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/module-regression--ba6eb4