Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation

MITAuto-check passedTesting & QA

Install TDD Guide

skills CLI
$ npx skills add alirezarezvani/claude-code-skill-factory --skill tdd-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-code-skill-factory tdd-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-code-skill-factory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/generated-skills/tdd-guide .claude/skills/tdd-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tdd-guide
GitHub stars
880
Used in
1 other repo
Token cost
~2.7k tokens
SKILL.md length
1,095 words
Files
15
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation

  • Works in 4 steps: Start with Requirements: Write tests… → Test Behavior, Not Implementation: Focus… → One Assertion Focus: Each test should… → …
  • Tasks that involve Test-driven development
  • SKILL.md covers Capabilities, Input Requirements, Output Formats and How to Use, plus 2 more sections
  • Runs Python scripts from its folder

What it does

TDD Guide is an agent skill from alirezarezvani/claude-code-skill-factory. Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files (for example `HOW_TO_USE.md`, `README.md` and `coverage_analyzer.py`).

It sits in Testing & QA, covering Test-driven development and Test generation. The repository describes itself as: Claude Code Skill Factory — A powerful open-source toolkit for building and deploying production-ready Claude Skills, Code Agents, custom Slash Commands, and LLM Prompts at… The licence is MIT.

When your agent uses it

  • Tasks that involve Test-driven development
  • Tasks that involve Test generation

Example prompts

  • “/tdd-guide”

Requirements

  • Python 3
  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Start with Requirements: Write tests from user stories before seeing implementation
  2. Test Behavior, Not Implementation: Focus on what code does, not how it does it
  3. One Assertion Focus: Each test should verify one specific behavior
  4. Descriptive Names: Test names should read like specifications

What it can do on your machine

Read from SKILL.md and the folder at commit ba18b31. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TDD Guide loads about 2.7k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 1,095 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alirezarezvani/claude-code-skill-factory at commit ba18b31, republished under its MIT licence (© alirezarezvani). 1,095 words, ~2,727 tokens.

Download SKILL.mdSave it as .claude/skills/tdd-guide/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
tdd-guide
description
Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation

TDD Guide - Test Driven Development for Engineering Teams

A comprehensive Test Driven Development skill that provides intelligent test generation, coverage analysis, framework integration, and TDD workflow guidance across multiple languages and testing frameworks.

Capabilities

Test Generation
  • Generate Test Cases from Requirements: Convert user stories, API specs, and business requirements into executable test cases
  • Create Test Stubs: Generate test function scaffolding with proper naming, imports, and setup/teardown
  • Generate Test Fixtures: Create realistic test data, mocks, and fixtures for various scenarios
TDD Workflow Support
  • Guide Red-Green-Refactor: Step-by-step guidance through TDD cycles with validation
  • Suggest Missing Scenarios: Identify untested edge cases, error conditions, and boundary scenarios
  • Review Test Quality: Analyze test isolation, assertions quality, naming conventions, and maintainability
Coverage & Metrics Analysis
  • Calculate Coverage: Parse LCOV, JSON, and XML coverage reports for line/branch/function coverage
  • Identify Untested Paths: Find code paths, branches, and error handlers without test coverage
  • Recommend Improvements: Prioritized recommendations (P0/P1/P2) for coverage gaps and test quality
Framework Integration
  • Multi-Framework Support: Jest, Pytest, JUnit, Vitest, Mocha, RSpec adapters
  • Generate Boilerplate: Create test files with proper imports, describe blocks, and best practices
  • Configure Test Runners: Set up test configuration, coverage tools, and CI integration
Comprehensive Metrics
  • Test Coverage: Line, branch, function coverage with gap analysis
  • Code Complexity: Cyclomatic complexity, cognitive complexity, testability scoring
  • Test Quality: Assertions per test, isolation score, naming quality, test smell detection
  • Test Data: Boundary value analysis, edge case identification, mock data generation
  • Test Execution: Timing analysis, slow test detection, flakiness detection
  • Missing Tests: Uncovered edge cases, error handling gaps, missing integration scenarios

Input Requirements

The skill supports automatic format detection for flexible input:

Source Code
  • Languages: TypeScript, JavaScript, Python, Java
  • Format: Direct file paths or copy-pasted code blocks
  • Detection: Automatic language/framework detection from syntax and imports
Test Artifacts
  • Coverage Reports: LCOV (.lcov), JSON (coverage-final.json), XML (cobertura.xml)
  • Test Results: JUnit XML, Jest JSON, Pytest JSON, TAP format
  • Format: File paths or raw coverage data
Requirements (Optional)
  • User Stories: Text descriptions of functionality
  • API Specifications: OpenAPI/Swagger, REST endpoints, GraphQL schemas
  • Business Requirements: Acceptance criteria, business rules
Input Methods
  • Option A: Provide file paths (skill will read files)
  • Option B: Copy-paste code/data directly
  • Option C: Mix of both (automatically detected)

Output Formats

The skill provides context-aware output optimized for your environment:

Code Files
  • Test Files: Generated tests (Jest/Pytest/JUnit/Vitest) with proper structure
  • Fixtures: Test data files, mock objects, factory functions
  • Mocks: Mock implementations, stub functions, test doubles
Reports
  • Markdown: Rich coverage reports, recommendations, quality analysis (Claude Desktop)
  • JSON: Machine-readable metrics, structured data for CI/CD integration
  • Terminal-Friendly: Simplified output for Claude Code CLI
Smart Defaults
  • Desktop/Apps: Rich markdown with tables, code blocks, visual hierarchy
  • CLI: Concise, terminal-friendly format with clear sections
  • CI/CD: JSON output for automated processing
Progressive Disclosure
  • Summary First: High-level overview (<200 tokens)
  • Details on Demand: Full analysis available (500-1000 tokens)
  • Prioritized: P0 (critical) → P1 (important) → P2 (nice-to-have)

How to Use

Basic Usage
@tdd-guide

I need tests for my authentication module. Here's the code:
[paste code or provide file path]

Generate comprehensive test cases covering happy path, error cases, and edge cases.
Coverage Analysis
@tdd-guide

Analyze test coverage for my TypeScript project. Coverage report: coverage/lcov.info

Identify gaps and provide prioritized recommendations.
TDD Workflow
@tdd-guide

Guide me through TDD for implementing a password validation function.

Requirements:
- Min 8 characters
- At least 1 uppercase, 1 lowercase, 1 number, 1 special char
- No common passwords
Multi-Framework Support
@tdd-guide

Convert these Jest tests to Pytest format:
[paste Jest tests]

Scripts

Core Modules
  • test_generator.py: Intelligent test case generation from requirements and code
  • coverage_analyzer.py: Parse and analyze coverage reports (LCOV, JSON, XML)
  • metrics_calculator.py: Calculate comprehensive test and code quality metrics
  • framework_adapter.py: Multi-framework adapter (Jest, Pytest, JUnit, Vitest)
  • tdd_workflow.py: Red-green-refactor workflow guidance and validation
  • fixture_generator.py: Generate realistic test data and fixtures
  • format_detector.py: Automatic language and framework detection
Utilities
  • complexity_analyzer.py: Cyclomatic and cognitive complexity analysis
  • test_quality_scorer.py: Test quality scoring (isolation, assertions, naming)
  • missing_test_detector.py: Identify untested paths and missing scenarios
  • output_formatter.py: Context-aware output formatting (Desktop vs CLI)

Best Practices

Test Generation
  1. Start with Requirements: Write tests from user stories before seeing implementation
  2. Test Behavior, Not Implementation: Focus on what code does, not how it does it
  3. One Assertion Focus: Each test should verify one specific behavior
  4. Descriptive Names: Test names should read like specifications
TDD Workflow
  1. Red: Write failing test first
  2. Green: Write minimal code to make it pass
  3. Refactor: Improve code while keeping tests green
  4. Repeat: Small iterations, frequent commits
Show full SKILL.md (454 more words)Show less
Coverage Goals
  1. Aim for 80%+: Line coverage baseline for most projects
  2. 100% Critical Paths: Authentication, payments, data validation must be fully covered
  3. Branch Coverage Matters: Line coverage alone is insufficient
  4. Don't Game Metrics: Focus on meaningful tests, not coverage numbers
Test Quality
  1. Independent Tests: Each test should run in isolation
  2. Fast Execution: Keep unit tests under 100ms each
  3. Deterministic: Tests should always produce same results
  4. Clear Failures: Assertion messages should explain what went wrong
Framework Selection
  1. Jest: JavaScript/TypeScript projects (React, Node.js)
  2. Pytest: Python projects (Django, Flask, FastAPI)
  3. JUnit: Java projects (Spring, Android)
  4. Vitest: Modern Vite-based projects

Multi-Language Support

TypeScript/JavaScript
  • Frameworks: Jest, Vitest, Mocha, Jasmine
  • Runners: Node.js, Karma, Playwright
  • Coverage: Istanbul/nyc, c8
Python
  • Frameworks: Pytest, unittest, nose2
  • Runners: pytest, tox, nox
  • Coverage: coverage.py, pytest-cov
Java
  • Frameworks: JUnit 5, TestNG, Mockito
  • Runners: Maven Surefire, Gradle Test
  • Coverage: JaCoCo, Cobertura

Limitations

Scope
  • Unit Tests Focus: Primarily optimized for unit tests (integration tests require different patterns)
  • Static Analysis Only: Cannot execute tests or measure actual code behavior
  • Language Support: Best support for TypeScript, JavaScript, Python, Java (other languages limited)
Coverage Analysis
  • Report Dependency: Requires existing coverage reports (cannot generate coverage from scratch)
  • Format Support: LCOV, JSON, XML only (other formats need conversion)
  • Interpretation Context: Coverage numbers need human judgment for meaningfulness
Test Generation
  • Baseline Quality: Generated tests provide scaffolding, require human review and refinement
  • Complex Logic: Advanced business logic and integration scenarios need manual test design
  • Mocking Strategy: Mock/stub strategies should align with project patterns
Framework Integration
  • Configuration Required: Test runners need proper setup (this skill doesn't modify package.json or pom.xml)
  • Version Compatibility: Generated code targets recent stable versions (Jest 29+, Pytest 7+, JUnit 5+)
When NOT to Use This Skill
  • E2E Testing: Use dedicated E2E tools (Playwright, Cypress, Selenium)
  • Performance Testing: Use JMeter, k6, or Locust
  • Security Testing: Use OWASP ZAP, Burp Suite, or security-focused tools
  • Manual Testing: Some scenarios require human exploratory testing

Example Workflows

Workflow 1: Generate Tests from Requirements
Input: User story + API specification
Process: Parse requirements → Generate test cases → Create test stubs
Output: Complete test files ready for implementation
Workflow 2: Improve Coverage
Input: Coverage report + source code
Process: Identify gaps → Suggest tests → Generate test code
Output: Prioritized test cases for uncovered code
Workflow 3: TDD New Feature
Input: Feature requirements
Process: Guide red-green-refactor → Validate each step → Suggest refactorings
Output: Well-tested feature with clean code
Workflow 4: Framework Migration
Input: Tests in Framework A
Process: Parse tests → Translate patterns → Generate equivalent tests
Output: Tests in Framework B with same coverage

Integration Points

CI/CD Integration
  • Parse coverage reports from CI artifacts
  • Generate coverage badges and reports
  • Fail builds on coverage thresholds
  • Track coverage trends over time
IDE Integration
  • Generate tests for selected code
  • Run coverage analysis on save
  • Highlight untested code paths
  • Quick-fix suggestions for test gaps
Code Review
  • Validate test coverage in PRs
  • Check test quality standards
  • Identify missing test scenarios
  • Suggest improvements before merge

Version Support

  • Node.js: 16+ (Jest 29+, Vitest 0.34+)
  • Python: 3.8+ (Pytest 7+)
  • Java: 11+ (JUnit 5.9+)
  • TypeScript: 4.5+

This skill works well with:

  • code-review: Validate test quality during reviews
  • refactoring-assistant: Maintain tests during refactoring
  • ci-cd-helper: Integrate coverage in pipelines
  • documentation-generator: Generate test documentation

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files in generated-skills/tdd-guide of alirezarezvani/claude-code-skill-factory.

  • SKILL.md
  • HOW_TO_USE.md
  • README.md
  • coverage_analyzer.py
  • expected_output.json
  • fixture_generator.py
  • format_detector.py
  • framework_adapter.py
  • metrics_calculator.py
  • output_formatter.py
  • sample_coverage_report.lcov
  • sample_input_python.json
  • sample_input_typescript.json
  • tdd_workflow.py
  • test_generator.py

Open the folder on GitHubat commit ba18b31

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-code-skill-factory, which our catalogue first saw on October 7, 2026.

Compare with similar skills

TDD Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TDD Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TDD Guide this skillalirezarezvani/claude-code-skill-factory8801 repos~2.7kAutomated safety check: PassMIT
Designing TestsCloudAI-X/opencode-workflow275—~2.9kAutomated safety check: PassMIT
Automated Test Planningtestdouble/han279—~6.7kAutomated safety check: PassMIT
Workflow Test GenerationdavidYichengWei/agentic-engineering-framework158—~580Automated safety check: PassMIT
TDDparcadei/Continuous-Claude-v33.9k1 repos~2.3kAutomated safety check: PassMIT
Manual Test Planningtestdouble/han279—~2.9kAutomated safety check: PassMIT

Similar skills

  • Designing Tests

    CloudAI-X/opencode-workflow

    Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.

    275 GitHub stars~2.9k tokensUpdated 9 mo ago
    Testing & QAAuto-check passed
  • Produce a standalone test plan by analyzing code for test coverage gaps and edge cases.

    279 GitHub stars~6.7k tokensUpdated 7 days ago
    Testing & QAAuto-check passed
  • Workflow Test Generation

    davidYichengWei/agentic-engineering-framework

    测试生成。基于 spec.md 或被测代码,生成单元测试、集成测试、性能测试。当用户请求生成测试、TDD 模式、或 workflow-code-generation 完成后触发。

    158 GitHub stars~580 tokensUpdated 6 mo ago
    Testing & QAAuto-check passed
  • TDD

    parcadei/Continuous-Claude-v3

    Test-driven development workflow with philosophy guide - plan → write tests → implement → validate

    3.9k GitHub starsUsed in 1 repo~2.3k tokens
    Testing & QAAuto-check passed
  • Manual Test Planning

    testdouble/han

    Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by…

    279 GitHub stars~2.9k tokensUpdated 7 days ago
    Testing & QAAuto-check passed
  • Shift Left Testing

    proffesor-for-testing/agentic-qe

    Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix.

    494 GitHub stars~1.2k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

More from alirezarezvani/claude-code-skill-factory

All 12 skills in this repo
  • App Store Optimization

    alirezarezvani/claude-code-skill-factory

    Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store

    880 GitHub starsUsed in 8 repos~4.1k tokens
    Auto-check passed
  • Content Trend Researcher

    alirezarezvani/claude-code-skill-factory

    Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven…

    880 GitHub starsUsed in 2 repos~2.1k tokens
    Auto-check passed
  • Claude Md Enhancer

    alirezarezvani/claude-code-skill-factory

    Analyzes, generates, and enhances CLAUDE.md files for any project type using best practices, modular architecture support, and tech stack customization.

    880 GitHub stars~4.1k tokensUpdated 10 mo ago
    Auto-check passed
  • Agent Factory

    alirezarezvani/claude-code-skill-factory

    Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns

    880 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Codex CLI Bridge

    alirezarezvani/claude-code-skill-factory

    Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

    880 GitHub stars~2.2k tokensUpdated 10 mo ago
    Auto-check passed
  • Social Media Analyzer

    alirezarezvani/claude-code-skill-factory

    Analyzes social media campaign performance across platforms with engagement metrics, ROI calculations, and audience insights for data-driven marketing decisions

    880 GitHub starsUsed in 3 repos~772 tokens
    Auto-check passed

Categories

Questions about TDD Guide

What does TDD Guide do?

Comprehensive Test Driven Development guide for engineering subagents with multi-framework support, coverage analysis, and intelligent test generation. TDD Guide is an agent skill from alirezarezvani/claude-code-skill-factory.

When should I use TDD Guide?

TDD Guide fits situations like: tasks that involve Test-driven development; tasks that involve Test generation.

How do I install TDD Guide in Claude Code?

Run `npx skills add alirezarezvani/claude-code-skill-factory --skill tdd-guide -a claude-code`. Or copy the skill folder (generated-skills/tdd-guide in alirezarezvani/claude-code-skill-factory) into .claude/skills/tdd-guide in your project. Claude Code loads it when a task matches its description.

How do I install TDD Guide in Codex?

Run `npx skills add alirezarezvani/claude-code-skill-factory --skill tdd-guide -a codex`. Or copy the skill folder (generated-skills/tdd-guide in alirezarezvani/claude-code-skill-factory) into .agents/skills/tdd-guide in your project. Codex loads it when a task matches its description.

Can I use TDD Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-code-skill-factory --skill tdd-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tdd-guide, .gemini/skills/tdd-guide, .github/skills/tdd-guide and .opencode/skills/tdd-guide in your project.

What does TDD Guide need to run?

Going by SKILL.md and its folder, TDD Guide needs Python for the scripts in its folder. Our summary lists: Python 3; Node.js.

Does TDD Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TDD Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does TDD Guide use?

TDD Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TDD Guide use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TDD Guide?

Skills that share tags, products or a category with TDD Guide: Designing Tests (CloudAI-X/opencode-workflow, 275 stars), Automated Test Planning (testdouble/han, 279 stars), Workflow Test Generation (davidYichengWei/agentic-engineering-framework, 158 stars) and TDD (parcadei/Continuous-Claude-v3, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TDD Guide?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-code-skill-factory, which has 880 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on November 12, 2025.

Source: alirezarezvani/claude-code-skill-factory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.