Provides quality gates for assessing task complexity, clarifying requirements, tracking failed attempts, and escalating blocked work.
SkillScore91Maintained
Automatic
◆QA & Test Engineering pack
Last verified 9/2/2026
What it changes
Passed 20 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill91%
Checks it passed that the model alone missed
Names security-sentinel for security auditing.
Names tdd-enforcer for test coverage enforcement.
Names typescript-strict-guard for type safety validation.
and 15 more in the full report
8 fixed12 passed either way2 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+71%
Agent turns
0%
Response time
-17%
Model gemini-3.6-flashMeasured 9/2/2026v320 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
An internal API utility module contains several `console.log('debug output', data)` lines for debugging production flows. What does our implementation gate say about console log statements?
What was checked, without and with the skill
Checked
Without skill
With skill
States that console.log statements are strictly forbidden in code passing the implementation gate.
Missed
Passed
case-16 · gemini-3.6-flash · 9/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md274 linessingle file
Quality Gates (Checkpoint Framework)
When to Use
Before starting implementation (pre-implementation gate)
During implementation (implementation gate)
After writing tests (testing gate)
Before completing work (review gate)
Overview
Quality gates are checkpoints that prevent bugs from being committed. Every agent must pass these gates before proceeding.
Gate Framework
Pre-Implementation Gate
Must pass BEFORE writing any code:
Requirements fully understood
Architecture decision made
Types and interfaces planned
Dependencies identified
Security implications assessed
Pattern compliance verified
How to pass:
Read all related files and tests
Document understanding in brief plan
Identify which architectural patterns apply
List all types/interfaces needed
Check for security concerns (auth, input validation, etc.)