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,591 stars 94 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
42
Issue Health 10%
50
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
6 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

tdd

Use when writing production code that needs tests - new features, bug fixes, refactoring. Enforces RED-GREEN-REFACTOR cycle before any implementation.

22 Updated yesterday
fusengine
AI & Automation Listed

test-driven-development

Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.

4 Updated today
izyanrajwani
AI & Automation Solid

tdd

Use test-driven development for behavior-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, formatting-only, or purely mechanical chores unless explicitly requested.

50 Updated 4 days ago
youdotcom-oss