test-driven-development
Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
Quellinformationen
- Repository
- a5c-ai/babysitter
- Letzte Quellaktivität
- 1. Juni 2026 um 07:46
- Erkannte Sprache von SKILL.md
- Englisch
- Sterne
- 1.832
- Forks
- 113
Installationsoptionen
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Datei-Explorer
2 DateienSKILL.md wird angezeigt
SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau- name
- test-driven-development
- description
- Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob, Agent, AskUserQuestion
- graph
- {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}
- During implementation (write tests before code)
- When verifying step completion
## Process
1. **Specify tests first** - Define inputs, expected outputs, edge cases
2. **Write test code** - Create automated tests matching specification
3. **Implement production code** - Write code that passes the tests
4. **Verify** - Run tests and confirm all pass
## Test Categories
- **Unit tests**: Isolated function/method testing
- **Integration tests**: Cross-component interaction testing
- **Manual verification**: Human-performed checks when automation is impractical
## Key Rules
- Never combine test writing and implementation into a single step
- Every task with code changes must have associated tests
- Tests must be runnable and produce clear pass/fail results
- Edge cases must be explicitly considered
## Tool Use
Integrated into `methodologies/rpikit/rpikit-plan` and `methodologies/rpikit/rpikit-implement`
Auf GitHub ansehen