菜单
Test-Driven Development methodology enforcing RED-GREEN-REFACTOR cycle. Use for writing tests first, preventing regression, and ensuring code correctness. Based on obra/superpowers.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill tdd-obra命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Write outbound email and external messages in Vamsee Achanta's voice — a subtle offer to help, never bold or rash claims. Load before drafting ANY email, LinkedIn/Collide reply, proposal note, or outreach sent under his name.
Save/publish analysis or computation results from ANY ecosystem repo to Hugging Face as a queryable, viewer-renderable dataset. Use when the user wants to "save results to hugging face", "publish dataset to HF", "hugging face data saving", "save analysis results", "hf dataset", "make results queryable", or "render via datasets-server API". Reshapes nested results into flat parquet tables, writes a dataset card with a viewer `configs:` block and provenance, applies license/public-vs-private routing, enforces a domain data-quality gate (faithful-to-source != correct), publishes to `aceengineer/<repo>-<projection>`, and verifies via the datasets-server API.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
基于 SOC 职业分类
正在显示 SKILL.md
| name | tdd-obra |
| description | Test-Driven Development methodology enforcing RED-GREEN-REFACTOR cycle. Use for writing tests first, preventing regression, and ensuring code correctness. Based on obra/superpowers. |
| type | reference |
| version | 1.0.0 |
| category | development |
| last_updated | "2026-01-19T00:00:00.000Z" |
| source | https://github.com/obra/superpowers |
| related_skills | ["systematic-debugging","writing-plans","subagent-driven"] |
| capabilities | [] |
| requires | [] |
| see_also | [] |
| tags | [] |
This skill enforces strict test-first development methodology. The core principle: "Write the test first. Watch it fail. Write minimal code to pass." If you didn't watch the test fail, you don't know if it tests the right thing.
Produce no production code without a failing test first.
Any code written before tests must be deleted entirely - no exceptions for keeping it as reference material.
Write one minimal test demonstrating desired behavior:
Run tests and confirm:
Write simplest code passing the test:
Confirm:
After green only, clean up implementation:
| Approach | Validates |
|---|---|
| Tests-first | "What should this do?" |
| Tests-after |
| "What did I build?" |
Tests written after code:
These are "Red Flags" requiring complete restart with proper TDD:
1. Write failing test reproducing the bug
2. Verify test fails for expected reason
3. Implement minimal fix
4. Verify all tests pass
5. Refactor if needed
6. Commit with test and fix together
Before completing work:
| Error | Cause | Solution |
|---|---|---|
| Test passes immediately | Wrote code first | Delete code, start over with test |
| Test errors instead of fails | Syntax or setup issue | Fix test setup, not production code |
| Tests pass but feature broken | Testing wrong thing | Review test assertions |
| Flaky tests | Async or state issues | Fix test isolation |
| Metric | Target | Description |
|---|---|---|
| Test-First Rate | 100% | Tests written before code |
| RED Verification | 100% | All tests watched failing |
| Coverage | >80% | Line coverage baseline |
| Critical Path Coverage | 100% | Auth, payments, security |
| Test Independence | 100% | No test order dependencies |