tdd-guide
Test-first development route for TDD, writing failing tests first, RED -> GREEN -> REFACTOR, and behavior-changing feature/bug/refactor work. Do not…
它会碰到什么
扫了多少1 个文本文件，2 KB
它会碰到什么不碰外部（只输出文字）
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
tdd-guide (Codex Compatibility)
Use this skill for all feature work, bug fixes, and refactors that change behavior.
Routing Boundary
Use this skill when the user wants to build or change behavior through tests:
- TDD / test-driven development
- write failing tests first
- test-first implementation
- RED -> GREEN -> REFACTOR
Do not use it when tests are already failing and the user wants root cause; route that to systematic-debugging. Do not use it when the user only wants a test/coverage report; route that to generating-test-reports.
Core Rule
No production code before a failing test.
Workflow
- RED
- Write one failing test for one behavior.
- Confirm the failure is expected.
- GREEN
- Implement the minimal code to pass.
- Re-run tests and keep scope narrow.
- REFACTOR
- Improve structure/naming without changing behavior.
- Keep all tests green.
- COVERAGE
- Verify coverage target (recommended >=80% for lines/functions/branches).
- Add missing tests for edge/error paths.
Minimum Test Set
- Unit: public functions and core logic.
- Integration: API/data/service boundaries.
- E2E: critical user path only when relevant.
Required Edge Cases
- Null/undefined input
- Empty values
- Invalid types
- Boundary values
- Error paths (network/DB/file)
- Concurrency-sensitive behavior
Vibe Integration
- Primary coding skill in M-grade flow.
- Compatible fallback target for
everything-claude-code:tdd-guide. - For richer TDD patterns, combine with
test-driven-development.
想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。