Agent skill · Testing & QA

strict-tdd

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

a5c-aigithub.com/a5c-aiGitHub ↗
claude-codecodexcan modify filesMIT
Install
npx skills add a5c-ai/babysitter --skill strict-tdd --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Version: 1.0.0
Declared author: babysitter-sdk
Allowed tools: Bash(*)ReadWriteEditGlobGrep
Path: library/methodologies/pilot-shell/skills/strict-tdd/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,642
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## TDD Cycle ### RED Phase 1. Write a test that captures exactly one acceptance criterion 2. Run the test -- it MUST fail 3. Verify it fails for the RIGHT reason (not a syntax error) 4. Commit: `test: add failing test for [criterion]` ### GREEN Phase 1. Write the MINIMUM code to make the test pass 2. Run the test -- it MUST pass 3. Verify only the target test turned green (no side effects) 4. Commit: `feat: implement [criterion]` ### REFACTOR Phase 1. Clean up code while keeping ALL tests green 2. Remove duplication, improve naming, extract methods 3. Run full test suite -- ALL tests MUST pass 4. Commit: `refactor: clean up [area]` ## Compliance Scoring | Score | Meaning | |-------|---------| | 90-100 | Exemplary TDD: all cycles followed correctly | | 70-89 | Good TDD: minor deviations | | 50-69 | Partial TDD: some implementation before tests | | 0-49 | TDD violation: significant implementation without tests | ## Verification Methods 1. **Git History Analysis**: Test files must appear in commits before implementation files 2. **Coverage Analysis**: New code must have >90% test coverage 3. **Commit Message Convention**: RED/GREEN/REFACTOR phases identifiable in messages

What's inside
Steps it walks through
  1. TDD Cycle
  2. RED Phase
  3. GREEN Phase
  4. REFACTOR Phase
  5. Compliance Scoring
  6. Verification Methods
Ships with 1 file
  • README.md
More from babysitter
All skills →
About this skill
What does the strict-tdd skill do?

Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.

How do I install it?

Run `npx skills add a5c-ai/babysitter --skill strict-tdd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going