test-driven-development
Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
来源信息
- 仓库
- a5c-ai/babysitter
- 最近来源活动
- 2026年6月1日 07:46
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 1,832
- 分支
- 113
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- 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`
在 GitHub 查看