adlc-tdd-validate

Score test suites from 0-100 and generate prioritized recommendations reports.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-tdd-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adlc-tdd-validate
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-tdd-validate
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-tdd-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quantify the quality of their tests and receive actionable recommendations to improve test suites.

Core Features & Use Cases

  • Scores test suites on a 0-100 scale and highlights key good practices.
  • Detects anti-patterns and suggests targeted improvements.
  • Generates a concise recommendations report suitable for CI checks and developer reviews.
  • Works with spec-kit projects that have a .specify/ directory.

Quick Start

Run the tdd-validate command on your project root to obtain a quality score and recommendations.

Frequently Asked Questions about adlc-tdd-validate

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

FAQPage Schema
How do I measure test suite quality and get a baseline score for my project?

To measure test suite quality, you can analyze your test files to receive a 0-100 score. This assessment highlights good practices, detects anti-patterns, and provides actionable recommendations to improve your tests.

How do I generate a test quality report for CI integration and developer review?

You can generate a concise test quality report by running the validation command on your project root. This outputs per-file and overall scores alongside prioritized recommendations suitable for CI checks and developer review.

Does test quality analysis require a specific project structure to work?

Yes, this test quality analysis is designed for projects following the spec-kit structure. It specifically requires a .specify/ directory in your repository to enable consistent test quality assessments across languages.

What is the best way to identify anti-patterns in my test suites?

The best way to identify test anti-patterns is to analyze test suites for targeted improvements. The analysis flags bad practices and outputs a prioritized recommendations report to guide developers in fixing them.

Can I use this test analysis tool across different programming languages and repositories?

Yes, you can use this test analysis tool across different languages and repositories. It relies on the spec-kit .specify/ directory structure to ensure consistent test quality assessments regardless of the underlying language.