Agent skill · Testing & QA

test-driven-development

Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.

GanyuanRangithub.com/GanyuanRanGitHub ↗
claude-codecodexMIT
Install
npx skills add GanyuanRan/Aegis --skill test-driven-development --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 17 KB
Bundled scripts: none
Path: skills/test-driven-development/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 902 · +79 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Execute → False-positive entry on a native-direct-skill host? → **Exit immediately unless the user explicitly asked for TDD or the conversation already contains `TDD Route: strict`.** In `off` mode, do not start RED / GREEN / REFACTOR from generic bugfix, contract, shared-module, or risky-code wording alone. Hand control back to `using-aegis`, `systematic-debugging`, `writing-plans`, or the fast path with verification. → Implementing a feature or bugfix under TDD Route `strict`? → **No production code without a failing test first.** Gate: medium/high complexity? → route to brainstorming or writing-plans first. Mode: default `off` disables automatic TDD, not completion verification; `auto` chooses strict/light/skipped by risk. Change Necessity: before strict RED/GREEN enters production edits, confirm the slice really needs a code change. Cycle: RED (write test → watch it fail) → GREEN (minimal code → watch it pass) → REFACTOR (clean up → keep green) Regression: shared module → related tests. contract change → producer + consumer. core logic → old + new tests. Ripple signal hit → cover producer+consumer or real user path before claiming green. GREEN proves the currently expressed b

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. TDD Mode and Route
  4. Preflight Gate
  5. Change Necessity
  6. Complexity Budget
  7. Pre-Edit Complexity Check
  8. Red-Green-Refactor
  9. RED - Write Failing Test
  10. Verify RED - Watch It Fail
  11. GREEN - Minimal Code
  12. Verify GREEN - Watch It Pass
  13. REFACTOR - Clean Up
  14. Repeat
Ships with 1 file
  • testing-anti-patterns.md
Commands it runs
npm test path/to/test.test.ts
npm test
PASS
More from Aegis
All skills →
About this skill
What does the test-driven-development skill do?

Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.

How do I install it?

Run `npx skills add GanyuanRan/Aegis --skill test-driven-development --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From GanyuanRan/Aegis, a repository with 902 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going