test-driven-development

仓库创建 2026年6月29日最近提交 22 天前SkillHot 收录 22 天前

⬈ GitHub 仓库 ⬈ SKILL.md 原文件 ⬇ Raw 原始文件

▸ 精选理由

帮助保持测试覆盖与实现正确性，适合开发与代码代理场景

这个 Skill 做什么

在实现功能或修复前遵循先写测试、再实现的 TDD 流程

先写测试、看它失败，再写最小实现让测试通过的开发流程，用来做新功能、修 Bug 或重构前后行为确认。任何需要保证行为正确和防止回归的场景都该用。特点是强调先看测试失败以验证测试有效，而不是事后补测试。

▸ 展开 SKILL.md 英文原文

Use when implementing any feature or bugfix, before writing implementation code

开发编程TDD测试优先测试驱动通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/test-driven-development/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/test-driven-development/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Test-Driven Development (TDD)

## Overview

Write the test first. Watch it fail. Write minimal code to pass.

**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.

**Violating the letter of the rules is violating the spirit of the rules.**

## When to Use

**Always:**
- New features
- Bug fixes
- Refactoring
- Behavior changes

**Exceptions (ask your human partner):**
- Throwaway prototypes
- Generated code
- Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

## The Iron Law

```
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
```

Write code before the test? Delete it. Start over.

**No exceptions:**
- Don'

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有