tdd-guide
This Claude Code subagent guides developers through test-driven development by enforcing a strict RED → GREEN → REFACTOR cycle. It restates behavior requirements, writes the smallest failing test first, implements minimal code to pass, then verifies before refactoring. Use it when a user explicitly requests TDD methodology or when a task is complex enough that failing tests should drive implementation from the start.
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/agents/tdd-guide.md -o ~/.claude/agents/tdd-guide.mdtdd-guide.md
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**
Use when creating or configuring Claude Code agents and their frontmatter.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.