test-driven-development

github:addyosmani/agent-skills · first seen 2026-10-30 · installs 65.4K · source · badge

Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug in it or change its behavior, even when the code is pasted inline and the request

Works with

tdd
Shares red, green, tdd, development
0.31
code-simplification
Shares pasted, changing, function, inline
0.22
debugging-and-error-recovery
Shares fixing, bug, reproduce, tests
0.21
source-driven-development
Shares development, implementing, fixing, driven
0.17
code-review-and-quality
Shares pasted, even, inline, bug
0.17

Used with

tdd
Shares red, green, tdd, development
0.31
code-simplification
Shares pasted, changing, function, inline
0.22
debugging-and-error-recovery
Shares fixing, bug, reproduce, tests
0.21
code-review-and-quality
Shares pasted, even, inline, bug
0.17
source-driven-development
Shares development, implementing, fixing, driven
0.17
incremental-implementation
Shares functionality, implementing, tests, test
0.16
diagnosing-bugs
Shares bug, loop, red, failing
0.15
verify-and-stop
Shares prove, focused, completion, proof
0.15
using-agent-skills
Shares development, arrives, discovered, implementing
0.15
constraint-driven-development
Shares development, tests, driven, green
0.14

Skill Health 100 (freshness and quality) estimated by backskills

Freshness 100 · Quality 100 · Efficacy not yet tested

Efficacy is shown once a skill has at least 10 use cases or a tools-enabled run. A small preliminary baseline has run and is not counted in this score.

Authors: run your own use cases with POST /api/skill-check (author-verified; never changes this public estimate). Paying never affects ranking. Author tests never change the public score. The public health score only breaks ties between equal matches.

Version history

2026-10-31T09:00:39+00:00 · sha256 8fcaa57cf445
2026-10-30T20:36:17 · sha256 a3aa6ba95638

Diff at 2026-10-31T09:00:39+00:00

--- previous
+++ current
@@ -245,6 +245,8 @@
 
 **Use mocks only when:** the real implementation is too slow, non-deterministic, or has side effects you can't control (external APIs, email sending). Over-mocking creates tests that pass while production breaks.
 
+For crash or rollback behavior, exercise the real boundary: an injected exception is not process termination, and a mocked transaction call is not a database rollback.
+
 ### Use the Arrange-Act-Assert Pattern
 
 ```typescript