Analyze project tests to produce a quality score and improvement recommendations.
npx skills add https://github.com/chaimt/GarminShabbatMode --skill tdd-validate
Please help me install this Agent Skill. Skill: tdd-validate Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/tdd-validate Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill tdd-validate
This skill helps teams measure test quality and identify actionable improvements by generating a numeric score and targeted recommendations.
Run tdd-validate at the root of your project to analyze tests, generate a quality score, and receive improvement recommendations.
High-intent search queries and answers about installing and using this skill.
To score test suite quality, run the analyzer at your project root to quantify tests and receive a numeric score with behavior-oriented refactoring recommendations. It requires a spec-kit style project structure containing a .specify/ directory to function correctly.
Test quality analysis evaluates unit and integration test suites to quantify their effectiveness and deliver improvement recommendations. It surfaces a numeric score and behavior-oriented findings that guide specific refactoring actions to improve overall code quality.
Yes, analyzing tests requires a spec-kit style project structure with a .specify/ directory. Without this specific directory structure, the analyzer cannot evaluate your unit and integration test suites or generate a quality score and recommendations.
Yes, you can evaluate both unit and integration test suites across typical software projects. The analysis works across standard test suites to surface a numeric score and behavior-oriented findings that guide targeted test refactoring.
To generate a test quality report for stakeholders, run the analysis at your project root. It outputs a detailed report containing the overall numeric score and actionable improvement recommendations suitable for stakeholder review.
Automated test quality scoring is limited by its requirement for a spec-kit style project structure with a .specify/ directory. It cannot analyze projects lacking this specific structure and focuses on behavior-oriented findings rather than executing the tests themselves.
chaimtAnalyze test suites to score quality and generate improvement plans.
JamkrisGuide test-first development with 80%+ coverage across unit, integration, and end-to-end tests.
GuidoBergmanScaffold a CI/CD quality pipeline with test execution, burn-in loops, and artifact collection.
christopherlouetDetect code smells and generate refactoring suggestions for JavaScript files.
