test-triage
Skill9 starsChanged 3 months agoApache-2.0View on GitHub
Rank the functions/modules changed this session by test-worthiness and output TEST / integration-only / SKIP per symbol. Uses graphify blast-radius when graphify-out/ exists, a static rubric otherwise. Use when you changed several units and are unsure which deserve a unit test, or before writing tests for a batch of new code.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- Hoerire/Azurtheir own version, first seen Nov 8, 2026
- MuhammadUsmanGM/claude-code-best-practicestheir own version, first seen Nov 1, 2026
- niki914/zafirotheir own version, first seen Oct 13, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- Thalisu/SKILLStheir own version, first seen Oct 1, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- openai/plugins★ 7.8ksame name
- niki914/zafiro★ 371same name
- MuhammadUsmanGM/claude-code-best-practices★ 105same name
- Hoerire/Azur★ 2same name
- MMACABRE/SKILLS★ 1same name
- Thalisu/SKILLS★ 1same 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 repository36 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- api-designSkill
- architectureSkill
- bash-linuxSkill
- batch-operationsSkill
- behavioral-modesSkill
- claude-code-worktreesSkill
- clean-codeSkill
- context-compressionSkill
- coordinator-modeSkill
- database-designSkill
- deployment-proceduresSkill
- documentation-templatesSkill
- error-handlingSkill
- github-issuesSkill
- github-pmSkill
- github-projectSkill
- git-workflowSkill
- goal-builderSkill
- graphifySkill
- intelligent-routingSkill
- lint-and-validateSkill
- lint-fixSkill
- memory-systemSkill
- performance-profilingSkill
- powershell-windowsSkill
- pre-commit-verifySkill
- red-team-tacticsSkill
- release-vsixSkill
- run-testsSkill
- server-managementSkill
- setup-testingSkill
- testing-patternsSkill
- uncle-bob-craftSkill
- vulnerability-scannerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
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 27
If it has logic, weigh amplifiers:
- Distinctive: line 36
Default: affected ≥ 3 → amplifier met (tune per project).
- Distinctive: line 38
Import-cycle membership = extra risk.
- Distinctive: line 60
Write tests only for TEST rows.
“Common” is measured: kept by at least 6 in 10 of the 4 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 triage — what to test among your changes
Decide which changed units deserve a unit test. Aid, not enforcer — you still decide.
Policy = .claude/rules/05-testing.md. This skill applies it to a batch, with
objective signals.
1. Collect changed symbols
Take the functions / modules you created or changed this session. Confirm with:
git status --shortandgit diff --name-only(uncommitted), orgit diff --name-only <base>...HEADif the work is committed.
List the concrete symbols (functions, classes, components) touched — not just files.
2. Score each symbol
TRIGGER first: does it have real logic (branch, loop, calculation, parser, non-trivial condition — ~CC ≥ 2)? No logic → SKIP (trivial getter, wrapper, pass-through, config, presentational UI).
If it has logic, weigh amplifiers:
- Business rule / money / security / auth → strong TEST.
- Reused / high fan-in / big blast radius → strong TEST.
- Pure presentational component, thin wrapper → SKIP or integration-only.
With graphify (graphify-out/graph.json exists)
graphify affected "<symbol>"— count of things that break if it changes. Default: affected ≥ 3 → amplifier met (tune per project).graphify explain "<symbol>"— degree + connections; high degree = extra risk.- Import-cycle membership = extra risk.
Without graphify
- Blast radius ≈ number of callers: search the repo for the symbol name.
- Judge logic + business/security by reading the code.
3. Output the triage table
One row per symbol:
| Symbol | Signal | Verdict | Why |
calcTax() | affected 7, business | TEST | tax rule, wide blast radius |
Badge.tsx | presentational | SKIP | styling-only |
wireRoutes() | affected 4, no logic | integration-only | glue, cover via 1 route test |
Verdicts: TEST (happy + edge), integration-only (cover via one higher-level test), SKIP (no value).
4. Act
Write tests only for TEST rows. State the SKIP / integration-only calls so the user can override. Do not pad SKIP symbols with empty tests.
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.

