test-gate
Skill0 starsChanged 17 days agoMITView on GitHub
Run the unit and integration suites, verify nothing was skipped, triage failures, and record merge-blocking evidence on the work item. Use before any handoff from execution to review, when asked to verify a change or run the tests, or when a pull request claims to be green.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- stigmer/stigmertheir own version, first seen Nov 8, 2026
- Jaxsbr/sabstheir own version, first seen Oct 20, 2026
- Giamme/kent-testtheir own version, first seen Oct 15, 2026
- BrentRector/claude-skillstheir own version, first seen Oct 3, 2026
- Kohulan/orthonym-skillstheir own version, first seen Sep 29, 2026
- gabrieldabbah/genesistheir own version, first seen Jul 28, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- stigmer/stigmer★ 9same name
- BrentRector/claude-skills★ 6same name
- gabrieldabbah/genesis★ 4same name
- Kohulan/orthonym-skills★ 2same name
- Docat0209/SoloForge★ 1same name
- Giamme/kent-test★ 1same name
- Jaxsbr/sabs★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- planner-executor-handoffSkill
- release-publishSkill
- research-loopSkill
- work-trackingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Clean checkout: Run the gates where stale state cannot flatter you: fresh clone or clean CI runner.
- Distinctive: line 40
Never widen a gate to let work through.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test gate
Goal: replace "should work" with exit codes on record. Phase doc:
docs/workflows/04-verification.md; standard: docs/standards/testing.md.
Procedure
- Clean checkout. Run the gates where stale state cannot flatter you: fresh clone or clean CI runner.
- Run both gates and capture exit codes:
make test-unit
make test-integration- Verify nothing was skipped. Skipped, pending, or deleted tests fail the gate even with exit 0. Diff the test list against the branch base if the framework does not report skips loudly.
- Triage failures on the ladder:
- flaky: rerun once; passing once means quarantine plus a work item, and the gate stays red until fixed
- environment: prove it (missing service, wrong version), then fix the environment, then rerun
- real: back to execution with the failing case attached
- Record evidence on the work item: trimmed gate output, skip count,
findings, verdict (
approvedorrejected: <what would flip it>).
Rules
- The gate is run by someone who did not write the change whenever possible; author-run gates are provisional.
- Exit codes are the interface. Suite output parsing, frameworks, and stacks are the consumer repo's business.
- Never widen a gate to let work through. A waived gate is a written human decision with a reason and an owner, recorded on the work item.
Quick reference
| Check | Passes when |
| unit suite | make test-unit exit 0 |
| integration suite | make test-integration exit 0 |
| skip audit | zero skipped or deleted tests |
| evidence | output and verdict posted on the work item |
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.