qa-gate

Creates YAML quality gate decision files with PASS, CONCERNS, FAIL, or WAIVED status for reviewed stories.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Gamaroff/agent-skills --skill qa-gate-gamaroff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-gate
Source: https://github.com/Gamaroff/agent-skills/tree/main/skills/qa-gate
Command: npx skills add https://github.com/Gamaroff/agent-skills --skill qa-gate-gamaroff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a story review, teams need a standardized, traceable record of the quality decision. This Skill formalizes review findings into a consistent YAML gate file with a clear PASS/CONCERNS/FAIL/WAIVED status, actionable issues, and rationale, so teams can make informed release decisions without ambiguity. ## Core Features & Use Cases - Deterministic Gate Decisions: Applies ordered rules based on risk scores, test coverage gaps, issue severity, and NFR statuses to derive the gate status consistently. - Standardized YAML Schema: Produces gate files with fixed severity values (low/medium/high), standard issue ID prefixes (SEC-, PERF-, TEST-), quality scores, and optional audit history. - Co-located Artifacts: Places gate files alongside the story or task they assess, mirroring the PRD directory structure rather than a central folder. - Use Case: After the qa-story skill reviews story 1.3 and finds missing rate limiting on auth endpoints, this Skill generates story.1.3.gate.1.auth-review.yml with a CONCERNS status, a high-severity SEC-001 issue, and a suggested fix. ## Quick Start Create a quality gate file for story 1.3 based on the completed QA review findings.

Frequently Asked Questions about qa-gate

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

FAQPage Schema
How do I create a quality gate file for a story?▼

Run the qa-gate skill after a story review is complete. It aggregates review findings, applies deterministic decision rules based on risk scores, severity, and NFR statuses, then writes a YAML gate file co-located with the story.

What gate statuses are available in a QA gate file?▼

Four statuses exist: PASS (no blocking issues), CONCERNS (non-blocking issues to track), FAIL (high-severity issues or unmet criteria), and WAIVED (issues explicitly accepted with a reason and approver).

Where are quality gate files stored?▼

Gate files are co-located in the same directory as the story or task they assess, following the naming format story.[epic].[story].gate.[number].[name].yml. They are never placed in a central docs/qa/gates folder.

How is the gate decision determined automatically?▼

Rules apply in order: risk scores of 9 or higher force FAIL, scores of 6 or higher force CONCERNS, high-severity issues force FAIL, medium-severity issues force CONCERNS, and failing NFRs force FAIL. Waivers override only with an active waiver, reason, and approver.

What severity values are allowed for gate issues?▼

Only low, medium, and high are permitted. Values like critical, severe, or minor are rejected to keep the schema predictable and machine-readable across all gate files.

Does a FAIL gate block the release pipeline?▼

No, gates are advisory checkpoints, not blocking mechanisms. They provide transparency about quality status, but the team chooses its own quality bar and decides whether to proceed.