agentleFS
Sign inStart free
yiweiwanyiweiwan/skills/.claude/skills/testing-quality/SKILL.md

testing-quality

Skill1 starsChanged 6 months agoMITView on GitHub

Use when adding, fixing, or improving tests, test strategy, coverage, mocks, fixtures, CI failures, flaky tests, unit tests, integration tests, end-to-end tests, visual tests, accessibility checks, or quality gates.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Add the smallest useful test at the lowest reliable level.

    line 12
  2. Distinctive:

    Use integration or end-to-end tests for cross-boundary behavior.

    line 13
  3. Distinctive:

    Keep tests deterministic, isolated, readable, and focused on stable behavior.

    line 14
  4. Distinctive:

    Prefer realistic fixtures over excessive mocking.

    line 18
  5. Distinctive:

    Test empty input, invalid input, permissions, not found, duplicates, concurrency, and partial failure.

    line 20
  6. Distinctive:

    Run the specific failing test first, then the nearest suite.

    line 24
  7. Distinctive:

    Run lint, typecheck, and build when test changes touch shared code.

    line 25

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

Testing Quality

Workflow

  1. Identify test framework, naming conventions, fixtures, factories, mocks, and CI commands.
  2. Reproduce the bug or define behavior before changing tests.
  3. Add the smallest useful test at the lowest reliable level.
  4. Use integration or end-to-end tests for cross-boundary behavior.
  5. Keep tests deterministic, isolated, readable, and focused on stable behavior.

Guidance

  • Prefer realistic fixtures over excessive mocking.
  • Mock network, time, randomness, external services, and slow boundaries deliberately.
  • Test empty input, invalid input, permissions, not found, duplicates, concurrency, and partial failure.

Verification

  • Run the specific failing test first, then the nearest suite.
  • Run lint, typecheck, and build when test changes touch shared 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.

Check your setup, free