skills.rest
jakubbartnik
jakubbartnikCOMMUNITY
Explore all skills by this author →
GitHub

test-driven-development

Enforces red-green-refactor TDD workflow requiring failing tests before production code.

Updated Aug 19, 2026
Search Tags:#code quality#unit tests#testing#tdd#pytest#regression#red-green-refactor
One-click install
npx skills add https://github.com/jakubbartnik/honey-barrel-finale --skill test-driven-development-jakubbartnik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven-development
Source: https://github.com/jakubbartnik/honey-barrel-finale/tree/main/honey-barrel-finale/workspace/hermes/skills/software-development/test-driven-development
Command: npx skills add https://github.com/jakubbartnik/honey-barrel-finale --skill test-driven-development-jakubbartnik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often write code first and add tests afterward, which produces tests that pass immediately and prove nothing about correctness. This Skill enforces strict test-driven development so every piece of production code is backed by a test that was watched failing first, catching bugs before commit and preventing regressions. ## Core Features & Use Cases - Red-Green-Refactor Enforcement: Guides the AI through writing a failing test, verifying the failure, writing minimal code to pass, and refactoring safely. - Rationalization Detection: Lists common excuses for skipping TDD and red flags that trigger deleting code and restarting with tests first. - Subagent Integration: Provides templates for delegating implementation tasks with TDD requirements embedded via delegate_task and terminal test commands. - Use Case: When fixing a bug, the Skill requires writing a failing test that reproduces the bug first, then implementing the minimal fix, ensuring the regression can never return undetected. ## Quick Start Ask the agent to implement a new feature or fix a bug using strict test-driven development with the red-green-refactor cycle.

Frequently Asked Questions about test-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I practice test-driven development with pytest?▼

Write one minimal failing test for a single behavior, run it with pytest to confirm it fails for the expected reason, then write the simplest code to make it pass. Finally run the full test suite to check for regressions before refactoring.

What is the red-green-refactor cycle in TDD?▼

Red means writing a failing test that defines the desired behavior. Green means writing the minimal code to make that test pass, even hardcoding values. Refactor means cleaning up duplication and names while keeping all tests green.

Should I write tests before or after writing code?▼

Write tests before code. Tests written after implementation pass immediately, which proves nothing about whether they test the right behavior. Watching a test fail first confirms it actually exercises the missing feature.

When is it acceptable to skip TDD?▼

Only for throwaway prototypes, generated code, or configuration files, and only after asking the user first. Exploration is fine, but the exploratory code must be discarded and reimplemented test-first.

What should I do if I already wrote code without tests?▼

Delete the code and start over with a failing test. Keeping it as reference leads to adapting it, which is effectively testing after. The sunk time is already gone; rewriting with TDD produces verifiable code.

Related Skills

Explore More Software Engineering Skills→
thesyntaxninjathesyntaxninja
2

test-driven-development

Write one failing test before implementation and outline RED-GREEN-REFACTOR steps.

Community
Intermediate
JunnnnyWonJunnnnyWon

smoke-check

Run the automated test suite and generate a PASS/FAIL smoke-test report.

Community
Intermediate
logo-solutionslogo-solutions

debugging-and-error-recovery

Guide systematic root-cause debugging of failing tests and build errors.

Official
Advanced
baphledbaphled
1

bdd-workflow

Define executable Gherkin specifications for RSpec, Ginkgo, and Jest workflows.

Community
Intermediate