agentleFS
soumatheusgomessoumatheusgomes/agentville/.claude/skills/test-triage/SKILL.md

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

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
  1. Distinctive:

    If it has logic, weigh amplifiers:

    line 27
  2. Distinctive:

    Default: affected ≥ 3 → amplifier met (tune per project).

    line 36
  3. Distinctive:

    Import-cycle membership = extra risk.

    line 38
  4. Distinctive:

    Write tests only for TEST rows.

    line 60

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 --short and git diff --name-only (uncommitted), or
  • git diff --name-only <base>...HEAD if 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:

SymbolSignalVerdictWhy
calcTax()affected 7, businessTESTtax rule, wide blast radius
Badge.tsxpresentationalSKIPstyling-only
wireRoutes()affected 4, no logicintegration-onlyglue, 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.