tdd-verify

Audit commit history and coverage to verify TDD compliance.

2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/michaelalber/ai-toolkit --skill tdd-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-verify
Source: https://github.com/michaelalber/ai-toolkit/tree/main/skills/tdd-verify
Command: npx skills add https://github.com/michaelalber/ai-toolkit --skill tdd-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that AI-generated code adheres to Test-Driven Development (TDD) principles, preventing common anti-patterns and improving overall code quality and maintainability.

Core Features & Use Cases

  • Commit History Analysis: Verifies if tests were committed before implementation.
  • Coverage Quality Audit: Assesses if tests provide meaningful coverage beyond just executing code.
  • TDD Anti-Pattern Detection: Identifies issues like over-mocking, implementation coupling, and assert-free tests.
  • Compliance Scorecard Generation: Provides a quantifiable score for TDD adherence.
  • Use Case: After an AI agent generates code for a new feature, use tdd-verify to audit the commits and tests to ensure TDD best practices were followed, providing a report on adherence and areas for improvement.

Quick Start

Run the tdd-verify skill to audit the TDD compliance of the current git branch.

Frequently Asked Questions about tdd-verify

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

FAQPage Schema
How do I audit AI-generated code for Test-Driven Development anti-patterns?

You can audit AI-generated code for Test-Driven Development anti-patterns by running an automated audit tool that analyzes commit history and coverage quality. It identifies over-mocking and implementation coupling to ensure test-first development discipline.

How does commit history analysis verify test-first development?

Commit history analysis verifies test-first development by checking if tests were committed before implementation code. This process audits git branches to confirm strict adherence to Test-Driven Development workflow and minimal implementation practices.

What is meaningful coverage quality in TDD and how is it assessed?

Meaningful coverage quality in TDD is assessed by evaluating whether tests actually assert behavioral outcomes rather than just executing code. The audit identifies assert-free tests and over-mocking to ensure tests provide genuine behavioral validation.

Can I get a quantifiable compliance scorecard for TDD adherence?

Yes, you can get a quantifiable compliance scorecard for TDD adherence. The audit generates a scorecard evaluating test-first development, behavioral testing, minimal implementation, and refactoring discipline, providing actionable recommendations for improvement.

What is the best way to detect over-mocking and implementation coupling in automated tests?

The best way to detect over-mocking and implementation coupling is to perform an automated TDD anti-pattern detection audit. This process scans test suites to identify behavioral testing flaws and generates actionable recommendations for improving code quality.

Does tdd-verify work without external testing dependencies?

Yes, tdd-verify operates without external testing dependencies. It directly analyzes your git branch's commit history and test code structure to audit TDD compliance, requiring no additional testing frameworks or environment setup.