Eng TDD

Fix a bug test-first when there is a clear, cheap regression test path. Use when the user asks for TDD, a failing test, or a regression test, or when the bug has an obvious cheap local test target.

23 stars 1 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jpoehnelt/skills --skill eng-tdd
Manual install
git clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/eng-tdd ~/.claude/skills/eng-tdd

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# TDD bug fix

Repo facts (from AGENTS.md or CLAUDE.md): the test policy (some repos require coverage for every behavior change, others allow a test only where a branch's behavior is uncertain), the test runner per package, and the single-test command. Follow the policy; when it rules out a new test, skip to the closest executable check below.

When the test path is clear and cheap, make the broken behavior executable before changing production code. The goal is a focused regression test that fails before the fix and passes after it.

Do not force a test when it is impractical: broad harness setup, brittle mocks, slow end-to-end infrastructure, production-only state, vague reproduction steps, or large unrelated fixture churn. Use the closest useful verification instead.

## Workflow

1. **Understand the bug.** Identify intended behavior, current behavior, the affected path, and the smallest observable reproduction.
2. **Choose the narrowest executable check.** Prefer the unit, component, or integration test style already used for that code, in the location the repo uses (often colocated as `foo.test.ts`), run with the repo's single-test command. If no practical path is obvious, do not create one just to satisfy the workflow.
3. **Write the failing test first.** Add the smallest test that would have caught the bug. It encodes intended behavior, not the current implementation.
Read the full skill on GitHub

Details

Skill name
eng-tdd
Path
eng-tdd/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Eng TDD skill do?

Fix a bug test-first when there is a clear, cheap regression test path. Use when the user asks for TDD, a failing test, or a regression test, or when the bug has an obvious cheap local test target.

How do I install the Eng TDD skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill eng-tdd. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Eng TDD popular?

It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.

Related skills

Agents Correct

23

jpoehnelt/skills

Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.

AI, LLMs & Agents

Agents Create Verification Skill

23

jpoehnelt/skills

Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.

AI, LLMs & Agents

Agents Reflect

23

jpoehnelt/skills

After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.

AI, LLMs & Agents

Eng Testing

23

jpoehnelt/skills

Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.

Testing & QA

Comms Interrogate

23

jpoehnelt/skills

Multi-reviewer critique of a diff, run as parallel read-only subagents from distinct angles, then synthesized into one verdict. Use for "interrogate", "adversarial review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".

Testing & QA

Dpia Generator

9

wnallen/dpia-generator

Use whenever the user wants to run, draft, or stress-test a Data Protection Impact Assessment or any jurisdiction's equivalent for a new or modified processing. Triggers: "run a DPIA on", "assess privacy risk for", "is this Article 35 / high risk?", "need a Colorado data protection assessment / LGPD RIPD / PIPL PIPIA / Law 25 PIA?", any new-processing description (tool, vendor, AI feature, monitoring) with a privacy-risk question, or a pasted vendor page with a GDPR/ICO/CNIL/EDPB/CPPA/ANPD question. Also "index our privacy notice" — a portable notice profile later runs check for policy drift.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.