regression-sentinel
Skill10 starsChanged yesterdayMITView on GitHub
Pre-flight and post-flight test suite baseline verification with automatic rollback on test failures
In this repository44 other files it gives its agents.
- llms-full.txtllms.txt
- llms.txtllms.txt
- ai-prompt-engineering-safety-reviewSkill
- ast-codemapSkill
- ast-grepSkill
- autoharnessSkill
- autonomous-backlog-driverSkill
- claude-kimi-mcp-normalizationSkill
- cli-self-updaterSkill
- code-frugalitySkill
- codemode-gatewaySkill
- codemode-typesSkill
- consequence-simulationSkill
- context-pruningSkill
- github-update-checkerSkill
- google-agents-cli-evalSkill
- google-agents-cli-scaffoldSkill
- history-searchSkill
- hook-gatingSkill
- hybrid-semantic-searchSkill
- kimi-code-agent-integrationSkill
- kimi-mcp-configurationSkill
- leann-vectorSkill
- log-summarizerSkill
- markdown-vagueSkill
- memory-reconciliationSkill
- mode-classificationSkill
- multiagent-orchestrationSkill
- output-compressionSkill
- prompt-injectionSkill
- python-anti-patternsSkill
- restart-trackingSkill
- rollback-guardSkill
- rust-call-graphSkill
- secrets-managementSkill
- security-best-practicesSkill
- session-compactorSkill
- sqlite-memorySkill
- swarm-barrierSkill
- swarm-dagSkill
- autoharnessSkill
- code-reliability-checksSkill
- skill-threat-rulesSkill
- autoharnessSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use during autonomous or batch task execution loops to protect codebase integrity by catching test regressions immediately and reverting …
- Distinctive: line 13
Check clean git working tree state or save SHA/stash.
- Very specific: line 14
Run baseline test suite command via autoharness sentinel run --pre-flight (or fast smoke test).
- Very specific: line 17
Use autoharness sentinel snapshot to checkpoint clean states.
- Very specific: line 19
Run full regression test suite via autoharness sentinel run.
- Distinctive: line 20
Verify AST anti-shim checks and test pass rate.
- Distinctive: line 21
If regression is detected:
- Distinctive: line 29
Test clean state approval: run verification on passing code, verify status passes.
- Distinctive: line 30
Test regression rejection: introduce an intentional syntax error or failing assertion, verify sentinel triggers rollback and returns …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Regression Sentinel
When to use
Use during autonomous or batch task execution loops to protect codebase integrity by catching test regressions immediately and reverting destructive modifications.
Steps
- Capture pre-flight baseline:
- Check clean git working tree state or save SHA/stash.
- Run baseline test suite command via
autoharness sentinel run --pre-flight(or fast smoke test).
- During task execution:
- Allow modifications within task workspace boundary.
- Use
autoharness sentinel snapshotto checkpoint clean states.
- Post-flight verification:
- Run full regression test suite via
autoharness sentinel run. - Verify AST anti-shim checks and test pass rate.
- Run full regression test suite via
- If regression is detected:
- Perform atomic rollback via
autoharness sentinel rollback(git restoreand clean untracked files). - Log the failure reason into
.autoharness/sentinel.jsonand.autoharness/drive_state.json. - Prevent downstream corrupted state from propagating.
- Perform atomic rollback via
- If verification succeeds:
- Approve state for commit and milestone completion.
How to verify
- Test clean state approval: run verification on passing code, verify status passes.
- Test regression rejection: introduce an intentional syntax error or failing assertion, verify sentinel triggers rollback and returns non-zero.
Facts found here
- Automated safety rollbacks eliminate the need for manual intervention during autonomous overnight runs.
- Running AST Anti-Shim detection alongside test execution prevents fake "passing" suites caused by empty mocks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

