skills.rest
aberrantCode
aberrantCodeCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with 80% coverage in JavaScript/TypeScript projects.

1|Updated Feb 26, 2026
Search Tags:#tdd#integration testing#unit testing#code coverage#javascript#test-driven development#e2e testing
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill tdd-workflow-aberrantcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/aberrantCode/llm_skills/tree/main/gemini/skills/tdd-workflow
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill tdd-workflow-aberrantcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the risk of low-quality code by mandating test‑first development and ensuring comprehensive test coverage across unit, integration, and end‑to‑end tests.

Core Features & Use Cases

  • Test‑First Discipline: Write failing tests before any implementation.
  • Coverage Enforcement: Require a minimum of 80 % combined coverage.
  • Multi‑Level Testing: Supports unit, integration, and Playwright E2E tests.
  • Applicable Scenarios: New feature development, bug fixes, refactoring, API endpoint creation, and new component implementation in JavaScript/TypeScript projects.

Quick Start

Ask the assistant to run the tdd‑workflow skill to generate failing tests for your new feature.

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 and maintain 80% code coverage in JavaScript?▼

You enforce test-driven development by mandating a test-first workflow that requires writing failing tests before any implementation, then iterating until all unit, integration, and E2E tests pass with a minimum of 80% combined coverage.

Can I use TDD workflows for bug fixes and API endpoint creation in TypeScript?▼

Yes, TDD workflows apply to bug fixes, refactoring, API endpoint creation, and new component implementation in JavaScript and TypeScript codebases by requiring failing tests first and iterating until they pass.

What is the best way to combine unit, integration, and E2E testing for new features?▼

The best way to combine multi-level testing is to enforce a test-first discipline that writes failing tests before implementation, ensuring at least 80% combined coverage across unit, integration, and Playwright E2E tests.

Does test-first development work with Playwright for end-to-end testing?▼

Yes, test-first development works with Playwright by supporting multi-level testing that includes unit, integration, and E2E tests, requiring you to write failing tests first and iterate until all tests pass.

How do I start writing failing tests before implementing a new feature?▼

To start writing failing tests, apply the test-first discipline to your new feature development by generating the initial failing tests before writing any implementation code, then iterate until all tests pass.

Why does test-driven development require failing tests before implementation?▼

Test-driven development requires failing tests before implementation to eliminate the risk of low-quality code by mandating test-first discipline and ensuring comprehensive coverage across unit, integration, and end-to-end tests.

Related Skills

Explore More Software Engineering Skills→
Dmccarty30Dmccarty30
4

using-git-worktrees

Create isolated Git worktrees with dependency installation and baseline tests.

Community
Intermediate
GainInsightDevGainInsightDev

af-analyse-test-coverage

Analyze test coverage reports to identify untested code paths and gaps.

Official
Intermediate
ihj04982ihj04982

test-coverage

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

Community
Advanced
vineethsomavineethsoma

tdd-workflow

Enforce Red → Green → Refactor commit cycles with TDD compliance checks before merging.

Community
Intermediate