test-runner
Skill0 starsChanged 8 months agoMITView on GitHub
Auto-invoke a test runner sub-agent to run tests and diagnose failures. Use when tests need to be run, when debugging test failures, or to verify implementation. Triggers: "run tests", "run the test suite", "check if tests pass", "why is this test failing", after implementing a fix, after completing GREEN phase of TDD, "test this".
19 other projects use a version of this.
Adopted by
Most recently taken up by
- d-o-hub/github-template-ai-agentstheir own version, first seen Nov 3, 2026
- claude-world/director-mode-litetheir own version, first seen Nov 1, 2026
- EffortlessMetrics/demo-swarmtheir own version, first seen Oct 17, 2026
- Mushfiqur-Rahman-Robin/coding-rulestheir own version, first seen Oct 13, 2026
- wanhaoli376-lab/AgentForgetheir own version, first seen Oct 11, 2026
- EmeaAppGbb/spec2cloudtheir own version, first seen Oct 9, 2026
Used with
Projects with it also use error-handling, code-reviewer and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillerror-handling
统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。
Also in 3 projects that use this
GoogleSkillcode-reviewer
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- openreview/openreview-py★ 273same name
- EmeaAppGbb/spec2cloud★ 100same name
- claude-world/director-mode-lite★ 80same name
- Kanevry/session-orchestrator★ 53same name
- amanning3390/hermeshub★ 48same name
- zircote/subcog★ 28same name
- Azure/sap-automation-qa★ 14same name
- leszekgruchala/buddy★ 6same name
- AskExe/exe-build-skills★ 4same name
- crgarcia12/Liliput★ 4same name
9 more not listed
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 repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ci-watchSkill
- commitSkill
- discovery-interview-prepSkill
- doc-generateSkill
- incident-responseSkill
- opportunity-solution-treeSkill
- polarisSkill
- prd-developmentSkill
- prioritization-advisorSkill
- reviewSkill
- roadmapSkill
- security-auditSkill
- session-wrapSkill
- spec-updateSkill
- tddSkill
- tech-debt-auditSkill
- user-storySkill
- uxSkill
- workshop-facilitationSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
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 32
If a specific test file was mentioned, pass it as context to the agent.
“Common” is measured: kept by at least 6 in 10 of the 18 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 Runner — Sub-agent Workflow
When to use (auto-trigger)
- After implementing code — verify nothing is broken
- When debugging a test failure — delegate diagnosis to the sub-agent
- Before /commit — ensure all tests pass (also handled by /commit quality gate)
- When switching context — run full suite to check baseline
- Never as a substitute for TDD — use /tdd for the Red-Green-Refactor cycle
Process
Delegate to the test-runner agent (.claude/agents/test-runner.md):
Use the Agent tool to spawn a test-runner sub-agent with subagent_type="general-purpose"
and model="haiku". The agent prompt is defined in .claude/agents/test-runner.md.The agent runs tests, parses failures, reads source files, and returns a structured diagnosis. It does NOT fix tests — it reports only.
If a specific test file was mentioned, pass it as context to the agent.
After the run
- All green: Proceed (suggest /commit if at a natural breakpoint)
- Failures found: Fix using TDD approach — the diagnosis guides the fix
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.