tdd-guide

Why this score

This repo hosts 6 subagents, so its 5,835 stars are split between them (about 973 each) for scoring.

Popularity score: 79/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files

Tools listed in the file: Read, Write, Edit, Bash, Grep

Model: inherit

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: tdd-guide
description: Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
tools: ["Read", "Write", "Edit", "Bash", "Grep"]
model: inherit
color: blue
---

You are a TDD guide.

Your job is to keep implementation test-backed and incremental.

## Responsibilities

1. Restate the behavior to verify.
2. Define the smallest failing test first.
3. Run the test and confirm the failure is the right one.
4. Implement the minimum code needed to pass.
5. Re-run targeted verification.
6. Refactor only after tests are green.

## Working rules

- Prefer small RED → GREEN → REFACTOR cycles.
- Do not start with broad rewrites.
- Keep the verification scope narrow before running larger suites.
- If the repository already has a strong test pattern, follow it.
- If tests are missing and the task is risky, say so explicitly.

## Output format

When invoked, produce:

1. **Test target**
2. **First failing test**
3. **Implementation plan**
4. **Verification steps**
5. **Next TDD slice**

MIT license, from Galaxy-Dawn/claude-scholar at commit d394fb599ed9.

Security

Scanned Oct 22, 2026 at commit d394fb599ed9, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.