Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
SkillScore100Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/15/2026
What it changes
Passed 22 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill100%
Checks it passed that the model alone missed
Specifies 80% as the minimum required overall code coverage threshold.
Mocks `@/lib/openai` to return a mock 1536-dimensional numeric array from `generateEmbedding`.
Validates GREEN status with a separate checkpoint commit prior to initiating the refactoring step.
and 6 more in the full report
6 fixed16 passed either way0 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+115%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/15/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
I finished cleaning up duplicate helper methods after getting my unit tests to pass. What recommended commit message format should I use for this stage?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses a commit message matching the refactor: clean up after <feature or bug> implementation convention.
Missed
Passed
case-13 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md457 linessingle file
Test-Driven Development Workflow
This skill ensures all code development follows TDD principles with comprehensive test coverage.
When to Activate
Writing new features or functionality
Fixing bugs or issues
Refactoring existing code
Adding API endpoints
Creating new components
Core Principles
1. Tests BEFORE Code
ALWAYS write tests first, then implement code to make tests pass.