超级能力 tdd
- 作者仓库星标 774
- 作者仓库 gemini-superpowers-antigravity
TDD Skill
When to use this skill
- new features that can be unit tested
- bug fixes (always add a regression test if practical)
- refactors (protect behavior with tests first)
Rules
- Prefer red -> green -> refactor.
- If tests are hard, still add verification: minimal repro script, integration test, or clear manual steps.
- Keep tests focused: one behavior per test where possible.
- Name tests by behavior, not implementation details.
Process
- Define the behavior change (what should be true after).
- Write/adjust a test to capture it (make it fail first if possible).
- Implement the minimal change to pass.
- Refactor if needed (keep passing).
- Run the relevant test suite + any linters.
Output requirements
When you change code, include:
- what tests you added/changed
- how to run them
- what they prove
- 流狐分类
- AI 智能
- 作者声明 Agent
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 作者 / 版本 / 许可
- @anthonylee991 · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 new features that can be unit tested bug fixes (always add a regression test if practical) refactors (protect behavior with tests first)
Prefer red -> green -> refactor. If tests are hard, still add verification: minimal repro script, integration test, or clear manual steps. Keep tests focused: one behavior per test where possible.
Define the behavior change (what should be true after). Write/adjust a test to capture it (make it fail first if possible). Implement the minimal change to pass.
When you change code, include: what tests you added/changed how to run them
# TDD Skill
## When to use this skill
- new features that can be unit tested
- bug fixes (always add a regression test if practical)
- refactors (protect behavior with tests first)
## Rules
- Prefer **red -> green -> refactor**.
- If tests are hard, still add **verification**: minimal repro script, integration test, or clear manual steps.
- Keep tests focused: one behavior per test where possible.
- Name tests by behavior, not implementation details.
## Process
1. Define the behavior change (what should be true after).
2. Write/adjust a test to capture it (make it fail first if possible).
3. Implement the minimal change to pass.
4. Refactor if needed (keep passing).
5. Run the relevant test suite + any linters.
## Output requirements
When you change code, include:
- what tests you added/changed
- how to run them
- what they prove 作者原文负责流程事实;流狐只索引当前章节、要点、文件与命令。
章节 -> When to use this skill → Rules → Process → Output requirements
要点 -> red -> green -> refactor · verification
文件/命令 -> Write/adjust · added/changed
内容 SHA-256 -> 8bb041232bc0
方法与流程
适用与边界
原文中的明确线索
Write/adjust、added/changed