Skip to content

oberconcejo/VS-CODE / .agents/skills/module-regression

module-regression

Verified

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.

FileKindSize
SKILL.mdskill md7.9 KB
templates/REGRESSION.example.mdmarkdown1.6 KB

templates/REGRESSION.example.md

View on GitHub
# REGRESSION.md — Module Regression Ledger

> After each relevant change, locate the changed module, run its acceptance command plus every required downstream command, and deliver only when all exit codes are green.
> Refresh downstream relationships from reproducible repository evidence. Acceptance commands are the core asset; prefer reconciliation against external facts over weak mocks or assertions.
> If a module has no acceptance command, mark it `MISSING`. Never manufacture a green result.
>
> Downstream evidence last refreshed: `<YYYY-MM-DD>` using `<verified repository scan command>`

## Module 01 — Data Ingestion

- Downstream consumers: `02-cleaning`, `03-shop-mapping`
- Dependency evidence: `MISSING` — replace after verification
- Regression acceptance command: `MISSING` — replace after verification
- Propagation rule: output column/format changes require 02 and 03; internal logging-only changes may exempt downstream when this module is green
- Last green commit: `<commit>`

## Module 02 — Cleaning

- Downstream consumers: `05-aggregation`
- Dependency evidence: `MISSING` — replace after verification
- Regression acceptance command: `MISSING` — replace after verification
- Propagation rule: external behavior changes require 05
- Related test points: `TEST-ORDER-001`, `TEST-AMOUNT-002`
- Last green commit: `<commit>`

## Module 04 — Temporary Utility

- Downstream consumers: none
- Dependency evidence: `MISSING` — replace after verification
- Regression acceptance command: `MISSING` — add the minimum executable check
- Propagation rule: none
- Related test points: `MISSING` — inventory in the test registry
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 193kUpdated Claude CodeCodexVerifiedInstall