JPeetz/agent-skills / skills/qa-testing/test-driven-development
test-driven-development
VerifiedUse this skill when implementing any logic, fixing any bug, or changing any behavior. Write a failing test before writing the code that makes it pass — PROVE it works before you trust it. Required for production code changes; skip only for pure configuration, documentation, or static content changes with no behavioral impact.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 406 B |
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 14.2 KB |
| evals/evals.json | config | 2.2 KB |
evals/evals.json
View on GitHub[
{
"id": "ev001",
"description": "RED phase — agent writes a failing test for unimplemented functionality",
"scenario": "User requests a 'TaskService.createTask' method that doesn't exist yet. Agent should write a test that calls createTask and asserts expected behavior (returns an object with id, title, status, createdAt).",
"expected_outcome": "Agent writes a test that FAILS because createTask is not defined — confirming RED phase compliance"
},
{
"id": "ev002",
"description": "GREEN phase — agent writes minimal code to pass the test",
"scenario": "Following the failing test from ev001, agent should implement createTask with just enough code to make the test pass — no extra fields, no validation beyond what the test asserts.",
"expected_outcome": "Agent implements a minimal createTask function that satisfies the test assertions without over-engineering"
},
{
"id": "ev003",
"description": "Prove-It Pattern — agent writes reproduction test for a bug before fixing",
"scenario": "User reports that completing a task doesn't set completedAt. Agent should first write a test that demonstrates the missing field, confirm it fails, then fix the code.",
"expected_outcome": "Agent writes a failing reproduction test before attempting the fix — confirming Prove-It Pattern compliance"
},
{
"id": "ev004",
"description": "REFACTOR phase — agent cleans up code without changing behavior",
"scenario": "After GREEN, the implementation has duplicated validation logic. Agent should extract the shared logic into a helper, keeping all tests passing.",
"expected_outcome": "Agent refactors the code, extracts shared logic, and verifies all tests still pass after refactoring"
},
{
"id": "ev005",
"description": "Error handling — agent uses REACT heuristic to find edge cases",
"scenario": "User asks agent to add error handling for a createTask endpoint. Agent should use the REACT heuristic (Range, Errors, Auth, Concurrency, Time) to identify edge cases systematically.",
"expected_outcome": "Agent identifies at least 3 edge case categories from REACT, writes tests for each, and implements error handling"
}
]Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |