Implementing with Tests

Implement runtime behavior changes and bug fixes with meaningful before-and-after checks, preserved behavior and relevant regression evidence. Use while editing code; prose-only changes do not need a failing test.

33 stars 4 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add okgrit/done-is-a-claim

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add okgrit/done-is-a-claim --skill implementing-with-tests
Manual install
git clone --depth 1 https://github.com/okgrit/done-is-a-claim.git /tmp/done-is-a-claim
mkdir -p ~/.claude/skills
cp -r /tmp/done-is-a-claim/skills/implementing-with-tests ~/.claude/skills/implementing-with-tests

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Implementing with tests

Make the requested behavior observable, change only what it needs, and preserve
the surrounding contract. Follow the user's explicit workflow choices; if they
override test-first work, record the resulting evidence limits without blocking
authorized implementation or pretending a failing baseline was observed.

## Choose the behavior boundary

Read the request, current code, relevant callers and existing tests. Identify
the behavior to change, inputs and outputs that expose it, and behavior that must
remain valid. Respect the assigned files and existing production code.

Select a check that distinguishes the requested outcome from a plausible defect.
Prefer the real affected boundary when a helper test or mocked success would miss
it. Assertions should follow the contract, not repeat implementation constants.
Include meaningful edge inputs and relevant preservation checks proportionately.

An existing passing test may already cover a preservation requirement or an
already implemented outcome. Run and inspect it; add a check only for a real
coverage gap. Do not force a failure for behavior that should stay unchanged.
For a prose-only edit, inspect the text and scoped diff and use relevant document
checks. Do not invent a runtime test or artificial red to satisfy a ceremony.

## Observe a useful baseline

For new or corrected behavior, write or select the smallest meaningful check
Read the full skill on GitHub

Details

Skill name
implementing-with-tests
Path
skills/implementing-with-tests/SKILL.md
License
Apache-2.0
Repo updated
25 October 2026

FAQ

What does the Implementing with Tests skill do?

Implement runtime behavior changes and bug fixes with meaningful before-and-after checks, preserved behavior and relevant regression evidence. Use while editing code; prose-only changes do not need a failing test.

How do I install the Implementing with Tests skill?

Claude Code plugin: /plugin marketplace add okgrit/done-is-a-claim. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Implementing with Tests popular?

It lives in okgrit/done-is-a-claim, which has 33 GitHub stars and 4 forks, and is included in 1 curated skill list.

Related skills

Acceptance Design

33

okgrit/done-is-a-claim

Define executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.

Testing & QAIn 1 list

Checking Delivery

33

okgrit/done-is-a-claim

Verify an artifact at its actual delivery destination and distinguish send attempts, acknowledgements, publication and consumer checks. Use when reporting a file, message, export or deployment as delivered; creating a local draft alone does not imply delivery.

DevOps & CloudIn 1 list

Collecting Worker Results

33

okgrit/done-is-a-claim

Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.

OtherIn 1 list

Reading Measurements

33

okgrit/done-is-a-claim

Read a number without being fooled by it: an exit code, a passing result file, a test count, a list size, a control run, a red or a green. Use before reporting any figure, before turning a test run into a verdict, before acting on 'N items are broken', and whenever two outputs or two counts of the same thing disagree.

Testing & QAIn 1 list

Analyze Experiments

48

amplitude/mcp-marketplace

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

Testing & QA12

Render QA and Surgical Changes

48

saranambiar/hyperframes-video-agent-skills

Verify final video renders and make tiny safe edits without breaking approved sync, including proof frames, contact sheets, media probing, stale theme scans, exact timestamp checks, carryover-frame refreshes, and re-render-only-affected-scenes workflows. Use when a user asks for final QA, HD/render verification, a small text/audio/color change, or regression checks after approved timing.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.