agentleFS
open-thoughtsopen-thoughts/OpenThoughts-Agent/.agents/skills/write-tests/SKILL.md

write-tests

Skill309 starsChanged 4 months agoApache-2.0View on GitHub

Write or revise tests with an emphasis on behavior, regression coverage, pytest style, and avoiding "slop tests." Use when adding tests, fixing failing tests, reviewing test quality, or deciding what test would catch a bug.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 5 projects that use this

  • LucasMatuszewskiSkill

    audit-agents

    Audit and maintain agent configuration files (.claude/agents, AGENTS.md, CLAUDE.md, agent-memory). Checks for duplicates, outdated info, naming conflicts, wrong technical facts, and files over 200 lines. Fixes all issues and commits.

    Also in 5 projects that use this

  • wolverin0Skill

    audit-decisions

    Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.

    Also in 4 projects that use this

  • rhnfzlSkill

    explore-unknowns

    Walk the user through mapping the unknowns of a task before, during, and after they build it, and hand them a four-quadrant map (settled ground, open decisions, taste, and landmines) they keep. Reach for this eagerly whenever a request is ambiguous or underspecified, the codebase or domain is unfamiliar, the user will "know it when they see it", a reference implementation must be understood before porting, a build-queue or architecture-changing task is about to start, a mid-build deviation needs capturing, or a finished change needs buy-in or verified understanding before merge. Trigger even when the skill is not named: "do a blindspot pass", "find my unknown unknowns", "interview me about this change", "brainstorm the approach for a task I am about to build", "help me scope this", "what am I missing here", "plan this before I build", "I know nothing about X in this codebase". When a territory profile is present it reads memory and the graph first and feeds the map into the build pipeline; without one it degrades to a plain general map. Not for trivial or mechanical tasks with clear acceptance criteria, single-fact lookups, pure debugging of a known symptom, or pure code review, those have their own tools. Do not use it to run the build itself; the map is the deliverable and implementation remains a separate task, whether it has not started or is already underway.

    Also in 5 projects that use this

  • +5 more from dzhng

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use this skill when a change needs tests or when existing tests look too coupled to implementation details.

    line 10
  2. Very specific:

    Read TESTING.md before writing or reviewing non-trivial tests.

    line 13
  3. Distinctive:

    Check for repo-specific testing rules for commands, markers, fakes, mocks, and numerical tolerances.

    line 22
  4. Distinctive:

    Write the smallest test that observes that behavior through a public API, structured output, persisted state, or real side effect.

    line 25
  5. Distinctive:

    Prefer a regression test before the fix when fixing a bug.

    line 27
  6. Distinctive:

    Keep test setup realistic but small.

    line 29
  7. Distinctive:

    Run the narrow test first, then the relevant package test command.

    line 31
  8. Very specific:

    Run the repo's test command over the test directories your change touches (e.g.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 73 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
<!-- Vendored from marin-community/marin-style v0.3.0 — do not edit; re-run `marin-style sync`. -->

Write Tests

Use this skill when a change needs tests or when existing tests look too coupled to implementation details.

Read TESTING.md before writing or reviewing non-trivial tests. It is the shared behavior-focused testing policy, also used by commit. Read AGENTS.md for the repo's coding standards. If the repo has package- or module-specific testing docs, read the nearest one for local commands, markers, fakes, mocks, and numerical tolerances before choosing a test style.

Workflow

  1. Find existing tests for the touched behavior before creating a new file.
  2. Check for repo-specific testing rules for commands, markers, fakes, mocks, and numerical tolerances.
  3. Name the behavior that should fail if the code is wrong.
  4. Write the smallest test that observes that behavior through a public API, structured output, persisted state, or real side effect.
  5. Prefer a regression test before the fix when fixing a bug. Ensure the test fails before implementing the bug fix.
  6. Keep test setup realistic but small. Use fixtures and parameterization to remove duplication.
  7. Run the narrow test first, then the relevant package test command. Before a PR, run the repo lint entry point required by AGENTS.md.

Default Commands

  • Run the repo's test command over the test directories your change touches (e.g. uv run pytest -m 'not slow').
  • For package-specific commands, use the relevant package testing doc.

For PR preparation, run infra/pre-commit.py --changed-files --fix or infra/pre-commit.py --all-files --fix as appropriate. Do not replace it with uv run pre-commit.

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.