← ClaudeAtlas

test-driven-developmentlisted

Implement behavior test-first with red, green, refactor; not auditing existing green checks.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# Test-Driven Development Use a focused red, green, refactor loop to guide a requested behavior change. Adapted from Addy Osmani's `test-driven-development` workflow; see the bundled license and repository third-party notice. ## Route precisely - Use when implementing a defined behavior or a diagnosed, reproducible bug where a useful automated test can run. If the cause is still unknown, use `debugging-and-error-recovery` to establish it first. - Use `prove-checks` when the task is to establish whether an existing green check could detect a defect. Use `code-review` for a read-only diff review. - For visual, operational, or otherwise hard-to-automate behavior, choose a proportionate executable check or observed manual verification and explain the limit; do not create a test that merely mirrors implementation. ## Discover the local test contract Read repository instructions, test locations, manifests, configuration, and CI commands. Identify the narrow runner for one case and the normal gate for the affected area. Preserve existing test style and working-tree changes. Do not assume a language, framework, or globally installed test command. ## Choose a discriminating observation Name the caller-visible boundary and the behavior one case will observe before writing the test. Use the existing contract and domain vocabulary; ask only when a missing decision changes the expected behavior. Do not require fresh approval for every test boundary already established by the task.