test-driven-development

Featured

Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.

AI & Automation 1,788 stars 106 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

## Non-Negotiable Rules - Always use run mode (`CI=true npm test` or `--run` flag) - NEVER use watch mode (prevents hanging processes) - Use timeout guards (`timeout 60s`) as backup - Record exit codes as evidence at each phase - If tests fail 3 consecutive times in GREEN, report failure status - Never skip RED phase (failing test must exist before implementation) - Never defer tests to "later" -- TDD means tests first ## Scope Discipline - If implementation requires >3 file changes, flag for scope review - Architectural choices require user approval unless pre-approved in plan - New dependencies require user approval ## When to Use - Every feature implementation in BUILD workflow - Every bug fix in DEBUG workflow (regression test) ## Agents Used - `component-builder` (primary consumer) - `bug-investigator` (regression tests)

Details

Author: a5c-ai
Repository: a5c-ai/babysitter
Created: 8 months ago
Last Updated: 6 days ago
Language: JavaScript
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

add-tdd

RED-GREEN-REFACTOR execution discipline for AI agents. Use when implementing any feature or bugfix that has (or should have) tests — forces a failing test confirmed for the right reason before any production code. Loaded by add.build.

8 Updated today

brabos-ai

AI & Automation Listed