Skills for “tdd”

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

…RSpec, Maven and Gradle. Use when the user asks to do TDD, work test-first, write the test first, follow red green refactor, build a feature test-driven from a spec or user story, or stop the agent from changing…

…feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename,…

…config option or a bug fix test-first, when the user says "TDD", "red-green" or "write the test first", or when a subagent is handed a ticket to…

Write the failing test first, then the code

You MUST use this when implementing testable behavior changes - new features, bug fixes, or refactors with observable contracts. Covers writing meaningful failing tests before implementation and verifying behavior…

…against a running system, and especially when following TDD or bug-diagnosis skills (such as `tdd` or `diagnosing-bugs`) in a repo whose live deployment runs on the same host, shares its `.env`, or is reachable from…

…a skill from Matt Pocock's skills repo (mattpocock/skills: tdd, diagnosing-bugs, grill-with-docs, to-spec, to-tickets, implement, code-review, and the rest) does the wrong thing in a real session. Use when the user…