agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/test-selection/SKILL.md

test-selection

Skill2 starsChanged 4 months agoMITView on GitHub

Use when an agent needs to choose appropriate verification scope after a change, balancing focused tests, package tests, typechecks, UI checks, and known residual risk.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Use after planning or making a change to decide which checks should run and which risks remain if some checks are skipped.

    line 10
  2. Distinctive:

    Run typecheck when changing exported types or TypeScript contracts.

    line 19
  3. Distinctive:

    Do not say "tested" without naming the check.

    line 33
  4. Distinctive:

    Do not rely only on snapshots or static reading for interactive UI behavior.

    line 34
  5. Distinctive:

    Do not run unrelated expensive suites just to look thorough when a narrower suite proves the change.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Selection

When to use

Use after planning or making a change to decide which checks should run and which risks remain if some checks are skipped.

Rules

  • Match test scope to blast radius.
  • For single-module logic, run the closest unit tests first.
  • For shared runtime/router/API behavior, add or run package-level tests.
  • For UI/browser-visible behavior, include Playwright or browser verification when feasible.
  • Run typecheck when changing exported types or TypeScript contracts.
  • Name skipped checks and why they were skipped.

Required output

When reporting, include:

  • Checks run.
  • Checks skipped.
  • Why the selected scope is sufficient.
  • Residual risk.

Forbidden actions

  • Do not say "tested" without naming the check.
  • Do not rely only on snapshots or static reading for interactive UI behavior.
  • Do not run unrelated expensive suites just to look thorough when a narrower suite proves the change.

Minimal example

Focused: SkillContextRouter.test.ts
Broader: AgentPlaybookCatalog.test.ts because manifest shape changed
Skipped: full shell typecheck due known pre-existing errors

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.

Check your setup, free