testing
/testing
Write tests red → green, one slice at a time, at agreed seams. Use when building a feature or fixing a bug test-first, or when another skill needs code driven by tests.
- Author
- fynnhaupt ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write tests red → green, one slice at a time, at agreed seams. Use when building a feature or fixing a bug test-first, or when another skill needs code driven by tests.
Original author description
Write tests red → green, one slice at a time, at agreed seams. Use when building a feature or fixing a bug test-first, or when another skill needs code driven by tests.
How it works
- Steps
SKILL.md preview
--- name: testing description: Write tests red → green, one slice at a time, at agreed seams. Use when building a feature or fixing a bug test-first, or when another skill needs code driven by tests. --- # Testing Drive code with tests: each test fails first, then just enough code makes it pass. Tests check **behaviour** through public interfaces, so they survive any refactor that keeps the behaviour. A **seam** is a public interface where you observe behaviour without reaching inside. Tests live at seams only. If the project has no test runner, tell the user and stop; this skill does not set one up. Ask the user every question, including a confirmation, through your harness's interactive question tool when it has one (e.g. `AskUserQuestion` in Claude Code), with the likely replies as options; show anything they must review, such as an issue body, as text first. Only without such a tool, type the question as text. ## Steps 1. **Agree the seams.** Take them from the spec's approach, if the work has a spec that names them. Otherwise propose seams on the critical paths and complex logic, and confirm them with the user. Done when every seam you will test is named and agreed. 2. **Read [TESTS.md](TESTS.md) and [MOCKING.md](MOCKING.md)** before the first test. Done when you have read both. 3. **Loop red → green**, one slice per cycle: write one test at a seam, run it and see it fail for the expected reason, then write only enough code to make it pass. For a bug, the first test reproduces it. Let each test build on what the last cycle taught you, rather than writing all tests up front. Name tests in the project's domain words. Done when every behaviour the work needs has a passing test at a seam, and all tests of the work pass together. Refactoring stays out of the loop; it belongs to review.
Files in this package (4)
- LICENSE 1 KB
- MOCKING.md 1 KB
- SKILL.md 2 KB
- TESTS.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · fynnhaupt/skills | 90 | MIT |
| iuliandita/skills | 100 | MIT |
| wrongstack/wrongstack | 100 | MIT |
| langwatch/langwatch | 100 | Apache-2.0 |
| mcouthon/agents | 100 | MIT |
| nteract/nteract | 100 | BSD-3-Clause |
| kettleofketchup/DraftForge | 100 | GPL-3.0 |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| TheBeardedBearSAS/claude-craft | 100 | MIT |
Database snapshot: 13.11.2026 · package version cb762a9b287e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100tdd
Test-driven development: the agent writes the failing test, then the code, one behavior at a time. Use when building a feature or fixing a bug test-first, or when the user says tdd, red-green, or test-first. - 100tdd
Test-first work in two modes: build a feature red → green at agreed seams, or fix a bug by writing the failing regression test first. Use when the user asks for TDD, red-green-refactor, a failing test, or a regression test, when `implement` builds a ticket, OR when a bug has an… - 100tdd
Test-driven development: red-green-refactor, one test per cycle. Use when the task asks to build a feature, fix a bug or change behaviour, before you write the code. - 90enable
Build one slice at a time with red-before-green tests at the agreed seams, tight feedback loops, and fresh-eyes review at every slice close. Use when the user asks to build a tracked piece of work or one of its slices (`/enable`, or in words) — including small work that never… - 100tdd
Build one feature or fix one bug test-first in the red → green → refactor loop, with tests at agreed seams. Use when the user asks for TDD or test-first work on a single feature or bug fix, mentions "red-green-refactor", wants integration tests, or when implement reaches its… - 100tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.