tdd-workflow

Enforce test-driven development with Git checkpoint commits for each TDD stage.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill tdd-workflow-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/tdd-workflow
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill tdd-workflow-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of untested code changes, inconsistent testing practices, and low test coverage that lead to production bugs, technical debt, and fragile codebases by enforcing a strict test-first development workflow.

Core Features & Use Cases

  • Test-First Enforcement: Requires writing failing tests before any production code is implemented for new features, bug fixes, and refactors.
  • Coverage Compliance: Mandates a minimum 80% test coverage across unit, integration, and end-to-end tests to ensure comprehensive validation.
  • Git Checkpoint Tracking: Automates creation of Git commits for each TDD stage (RED, GREEN, refactor) to provide clear progress tracking and audit trails.
  • Use Case: When building a new API endpoint, this Skill ensures you first write failing tests for the endpoint's expected behavior, implement the endpoint to pass the tests, then refactor the code while maintaining all passing tests and coverage requirements.

Quick Start

Use the tdd-workflow skill to implement the new user profile update feature with full test coverage and Git checkpoint commits for each TDD stage.

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?

Test-driven development is enforced by mandating failing tests before production code, achieving 80% coverage, and automating Git checkpoint commits for RED, GREEN, and refactor stages.

What is the best way to track TDD stages in Git?

Tracking TDD stages in Git is done by automating checkpoint commits for each phase, ensuring the RED, GREEN, and refactor stages provide a clear audit trail and progress tracking.

How do I ensure minimum code coverage when fixing bugs?

To ensure minimum code coverage when fixing bugs, this workflow mandates comprehensive unit, integration, and end-to-end tests with an 80% coverage threshold before changes reach production.

Can I use this test-first workflow for API endpoint creation?

Yes, you can use this test-first workflow for API endpoint creation by writing failing tests for expected behavior, implementing the endpoint to pass, and refactoring while maintaining coverage.

Does this TDD workflow require specific testing frameworks?

No specific testing frameworks are required as dependencies, allowing you to apply test-driven development, 80% coverage mandates, and Git checkpoints across any software engineering codebase.