skills.rest
linnefromice
linnefromiceCOMMUNITY
Explore all skills by this author →
Website𝕏@linnefromiceGitHub

tdd-workflow

Enforce test-driven development with test-first design and 80% coverage verification.

Updated Jan 22, 2026
Search Tags:#workflow#tdd#test-driven development#unit-testing#integration-testing#e2e-testing#test-coverage
One-click install
npx skills add https://github.com/linnefromice/claude-code-workspace --skill tdd-workflow-linnefromice
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/linnefromice/claude-code-workspace/tree/main/template-.claude/skills/tdd-workflow
Command: npx skills add https://github.com/linnefromice/claude-code-workspace --skill tdd-workflow-linnefromice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that software development is driven by tests, preventing untested changes and reducing regression risk by enforcing a test-first workflow.

Core Features & Use Cases

  • Test-first workflow: write tests that describe expected behavior before implementing code.
  • Coverage enforcement: aim for 80%+ test coverage across unit, integration, and end-to-end tests.
  • Practical scenarios: ideal for adding new features, fixing bugs, or refactoring while preserving quality.

Quick Start

  1. Write a failing unit test for a small function or feature.
  2. Implement the minimal code to make the test pass.
  3. Run the full test suite and verify that overall coverage meets or exceeds 80%.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce test-driven development for new features and bug fixes?▼

Enforce test-driven development by writing failing tests that describe expected behavior before implementing code. This workflow prevents untested changes and applies strictly to feature additions, bug fixes, and refactoring tasks.

What is the best way to maintain 80%+ test coverage during refactoring?▼

Maintain 80%+ test coverage by running the full test suite after implementing minimal code changes. Coverage verification ensures refactoring preserves quality and prevents regressions across unit, integration, and end-to-end tests.

Can I use a test-first workflow for unit, integration, and e2e testing?▼

Yes, the test-first workflow applies comprehensively to unit testing, integration testing, and end-to-end testing. It formalizes test-first design, green test verification, and coverage checks using common tooling across all test levels.

How does writing tests before implementing code reduce regression risk?▼

Writing tests before implementing code reduces regression risk by ensuring tests guide all feature work. This test-first design mandates that untested changes are prevented, formalizing a workflow where expected behavior is specified upfront.

When do I need to verify test coverage across my full test suite?▼

Verify test coverage across your full test suite after implementing the minimal code required to make failing tests pass. This ensures overall coverage meets or exceeds the 80% target during feature addition, bug fixing, or refactoring.

Related Skills

Explore More Software Engineering Skills→
vikas-gits-goodvikas-gits-good

testing-patterns

Standardize Jest and Playwright test workflows with RLS validation.

Community
Intermediate
DaniloUnicamDaniloUnicam

test-coverage-improver

Analyzes software test coverage and suggests targeted tests for improvement.

Community
Intermediate
gab3mionigab3mioni

laravel-static-analysis

Automate Laravel 12 static analysis, formatting, and refactoring with Pint, Larastan, Rector, and Pest.

Community
Advanced
Liuchun-ossLiuchun-oss
15

test-driven-development

Write failing tests before implementing minimal code in a red-green-refactor workflow.

Community
Advanced