agentleFS
mattpocockmattpocock/ai-hero-cli/.claude/skills/what-to-test/SKILL.md

what-to-test

Skill151 starsChanged 10 months agoMITView on GitHub

Use when writing tests, improving coverage, or deciding what to test in this CLI

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:

    Test user-facing behavior.

    line 11
  2. Distinctive:

    All CLI commands must be tested - including commands marked "internal".

    line 13
  3. Distinctive:

    Do NOT write tests just to increase coverage numbers.

    line 21
  4. Distinctive:

    Test error paths users will actually hit

    line 36
  5. Distinctive:

    Use v8 ignore for CLI formatting/presentation code

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

What to Test

Philosophy

Test user-facing behavior. If a user would notice it's broken, it needs a test.

All CLI commands must be tested - including commands marked "internal". Internal commands are still user-facing (Matt uses them daily).

What Makes a Good Test

  • Tests behavior users depend on
  • Validates real workflows, not implementation details
  • Catches regressions before users do

Do NOT write tests just to increase coverage numbers. Use coverage as a guide to find untested user-facing behavior.

What NOT to Test

Use /* v8 ignore start */ for:

  • Integration boundaries (actual git calls, shell execution, filesystem)
  • Service layers that get mocked in tests
  • Entry points and DI wiring
  • Boilerplate, unreachable error branches

Testing Pattern

  1. Export a runX() function from command files for testability
  2. Mock external services (GitService, PromptService)
  3. Test error paths users will actually hit
  4. Use v8 ignore for CLI formatting/presentation code

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.