skills.rest
oguzhanguvenkaya
oguzhanguvenkayaCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with 80%+ coverage across unit, integration, and E2E tests.

Updated May 1, 2026
Search Tags:#testing#tdd#e2e#playwright#coverage#unit-testing#integration-testing
One-click install
npx skills add https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations --skill tdd-workflow-oguzhanguvenkaya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/oguzhanguvenkaya/oguzhan_claude_code_configurations --skill tdd-workflow-oguzhanguvenkaya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing code without a disciplined test strategy leads to fragile software and high maintenance costs. This skill enforces test-driven development and ensures 80%+ coverage across unit, integration, and E2E tests, reducing regressions.

Core Features & Use Cases

  • Enforces tests-before-code discipline for new features, bug fixes, and refactoring.
  • Ensures minimum test coverage across unit, integration, and E2E tests using structured workflows.
  • Guides teams through crafting user journeys, generating test cases, running tests, and refactoring for quality.

Quick Start

Describe a feature you want to implement and the skill will guide you through writing tests, implementing code, and validating 80%+ test coverage.

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?▼

You can enforce test-driven development by automating a workflow that requires writing tests before implementation. This ensures a structured process for feature development and bug fixes, validating code through unit, integration, and E2E tests before refactoring.

What is the best way to maintain 80%+ test coverage across unit, integration, and E2E tests?▼

Maintaining 80%+ test coverage requires an automated TDD workflow that guides teams through crafting user journeys, generating test cases, and running tests. This structured approach validates comprehensive coverage across unit, integration, and E2E testing layers.

How does a TDD workflow handle refactoring without introducing regressions?▼

A TDD workflow handles refactoring by enforcing a tests-before-code discipline, ensuring existing tests validate changes. By running structured test suites throughout the refactoring process, it reduces regressions and maintains software quality.

Do I need Playwright to automate end-to-end testing in a TDD workflow?▼

Playwright is supported for end-to-end testing within this TDD workflow. The skill guides you through structured E2E validations alongside unit and integration tests to satisfy comprehensive testing requirements and achieve green tests.

Can I use this TDD workflow for both feature development and refactoring tasks?▼

Yes, this TDD workflow applies directly to feature development, bug fixes, and refactoring tasks. It guides teams from writing user journeys to achieving green tests, ensuring minimum coverage across all test layers for any code modification.

Related Skills

Explore More Software Engineering Skills→
GatsbyhateyouGatsbyhateyou

tdd-workflow

Enforces a Test-Driven Development workflow with test-first and coverage requirements.

Community
Advanced
ihj04982ihj04982

test-coverage

Analyzes JSON coverage reports and generates missing tests for files under 80% coverage.

Community
Advanced
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic