superpowers tdd
- Repo stars 774
- Author repo gemini-superpowers-antigravity
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @anthonylee991 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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
Sections and files
Listed in source order.
sections -> When to use this skill → Rules → Process → Output requirements
terms -> red -> green -> refactor · verification
files/cmd -> Write/adjust · added/changed
body sha256 -> 8bb041232bc0
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