no-pre-existing-failures
Skill0 starsChanged 8 months agoUnlicenseView on GitHub
Test accountability policy. All failures belong to the current changeset. Commits must include test results. No failures on main.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-optimizeSkill
- dev-recordSkill
- flesh-outSkill
- generator-codingSkill
- light-v-structureSkill
- review-skillSkill
- review-stepsSkill
- sandboxSkill
- sdlc-cross-reviewSkill
- strong-editSkill
- my-skillSkill
The file
Files
- Every test failure is caused by your changes. There are no "pre-existing," "known," "flaky," or "unrelated" failures. If a test fails, you broke it. Fix it before proceeding.
- Every git commit must include a test summary. On
main, all tests must pass — no exceptions. On branches, failures are permitted only if explicitly noted in the commit message with the failure name and reason.
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.