Strict tdd
Skill a5c-ai/babysitter/library/methodologies/pilot-shell/skills/strict-tdd
Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration
npx -y skills add a5c-ai/babysitter --skill strict-tddAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
SKILL.md
2.0 KB, as published. Nobody here has run it
TDD Cycle
RED Phase
- Write a test that captures exactly one acceptance criterion
- Run the test -- it MUST fail
- Verify it fails for the RIGHT reason (not a syntax error)
- Commit:
test: add failing test for [criterion]
GREEN Phase
- Write the MINIMUM code to make the test pass
- Run the test -- it MUST pass
- Verify only the target test turned green (no side effects)
- Commit:
feat: implement [criterion]
REFACTOR Phase
- Clean up code while keeping ALL tests green
- Remove duplication, improve naming, extract methods
- Run full test suite -- ALL tests MUST pass
- 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
- Git History Analysis: Test files must appear in commits before implementation files
- Coverage Analysis: New code must have >90% test coverage
- Commit Message Convention: RED/GREEN/REFACTOR phases identifiable in messages