Skip to content
Get packs

Module Regression Ledger

Checks that changing one module doesn't silently break the modules that depend on it.

Source Download skill
Repository
affaan-m/ECC
Stars
295,127
Licence
MIT
Files
3 files

What it does

Once installed, the agent keeps a REGRESSION.md file that lists each module in a large codebase, the modules that depend on it, and the test or reconciliation command that proves it still works. After you change code, the agent works out which modules are affected, plans the commands to run, and reports the exit codes as evidence. It is meant to catch downstream breakage that is only noticed days later. The agent plans and reports the checks; the commands themselves run through your trusted host environment.

Great for

  • Developers maintaining large repositories with several interdependent modules
  • Teams where a change to one module has previously broken another module
  • People who already have tests or reconciliation scripts they want organized by dependency

Skip it if

  • Small projects with no cross-module dependencies, where the ledger adds overhead without benefit
  • Projects where dependencies cannot be established mechanically: the skill marks such edges unverified and they block an all-green verdict until a human confirms them
  • Running it on untrusted repositories without review, because ledger commands are treated as untrusted content and may execute code on your machine

Try asking

  • “Use module-regression to audit which downstream modules need to rerun after my change to the data-cleaning module.”
  • “Create a REGRESSION.md ledger for this monorepo, listing each module's consumers and acceptance command.”
  • “Run a downstream verification for the changes in my current branch against the merge-base and report the exit codes.”
Step-by-step guide: how to use Module Regression LedgerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 3 original files, the MIT licence and an attribution note.

    module-regression.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip module-regression.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip module-regression.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Start with a small ledger covering only the modules that have known cross-module breakage, then expand it.
  • Keep change batches small so failures can be attributed to a specific change; record the last green commit in the ledger.
  • Review the bounded command list the agent proposes before approving execution, since the ledger's commands come from repository content.

What's inside

  • agents/openai.yaml
  • SKILL.md
  • templates/REGRESSION.example.md

Redistributed unmodified from affaan-m/ECC under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.