tdd-guide

Generate unit tests and analyze LCOV, JSON, and XML coverage reports.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mdnaimul22/human-skills --skill tdd-guide-mdnaimul22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-guide
Source: https://github.com/mdnaimul22/human-skills/tree/main/skills/tdd-guide
Command: npx skills add https://github.com/mdnaimul22/human-skills --skill tdd-guide-mdnaimul22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Teams struggle to consistently translate requirements into correct, maintainable tests while also closing coverage gaps and following a disciplined red-green-refactor workflow.

Core Features & Use Cases

  • Intelligent test generation: Create unit test cases, stubs, and fixtures from requirements, stories, and code context, with framework-aware structure.
  • Coverage analysis & gap fixing: Parse coverage reports (LCOV, JSON/Istanbul, XML/Cobertura) to find uncovered lines/branches and prioritize what to test next.
  • TDD workflow guidance: Step through RED, GREEN, and REFACTOR phases with validation checkpoints to help ensure tests fail for the right reasons and stay green after changes.

Real-world use case: You’re implementing a user-auth module and want the skill to generate tests for email/password validation, analyze your existing coverage report, then tell you the highest-priority missing test scenarios to reach your target threshold.

Quick Start

Use the tdd-guide skill to generate and scaffold Jest tests for a function you provide by replying with your source code, your framework preference (Jest), and the behaviors/requirements you want covered.

Frequently Asked Questions about tdd-guide

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

FAQPage Schema
How do I generate unit tests from requirements using Jest or Pytest?

Unit test generation accepts source code, framework intent, and requirements to produce framework-aware test cases, stubs, and fixtures. It scaffolds tests for Jest, Pytest, JUnit, and Vitest, translating behaviors into maintainable test structures.

How do I find uncovered lines and branches from an LCOV or Cobertura coverage report?

Coverage analysis parses LCOV, JSON/Istanbul, and XML/Cobertura formats to compute coverage summaries and identify uncovered logic. It highlights missing lines and branches, producing prioritized recommendations for which test scenarios to implement next.

Can I get step-by-step guidance for the red-green-refactor TDD workflow?

TDD workflow guidance steps through RED, GREEN, and REFACTOR phases with validation checkpoints. It ensures tests fail for the right reasons during RED, pass correctly during GREEN, and stay green after REFACTOR changes.

Does this work with JUnit and Vitest workflows or just Jest and Pytest?

Framework support extends to Jest, Pytest, JUnit, and Vitest workflows. The skill applies framework-aware structures to generate tests and validate red-green-refactor progress across all four testing frameworks.

What is the best way to prioritize missing test scenarios to reach a target coverage threshold?

Prioritized recommendations are generated by analyzing coverage gaps and computing summaries from parsed reports. The skill identifies the highest-priority missing test scenarios needed to reach your target threshold based on uncovered logic.

Why do I need to provide framework intent when generating test fixtures?

Framework intent is required because test generation creates framework-aware structures, stubs, and fixtures. Providing the target framework ensures the generated tests match the correct syntax and workflow for Jest, Pytest, JUnit, or Vitest.