qa-gate

Generates pass/fail quality gate files with severity-rated issues for story reviews.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill qa-gate-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-gate
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/qa/qa-gate
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill qa-gate-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent, auditable way to decide whether a reviewed story is ready to ship. This Skill produces a standardized quality gate file that records a clear PASS, CONDITIONAL, or FAIL decision with actionable feedback before code is merged or released. ## Core Features & Use Cases - Structured Gate Decisions: Evaluates stories in REVIEW status against acceptance criteria and outputs PASS, CONDITIONAL, or FAIL with a concise status reason. - Standardized Issue Tracking: Generates issue entries with fixed severity levels (low, medium, high) and prefixed IDs such as SEC-, PERF-, TEST-, and ARCH-. - Strict YAML Schema: Writes gate files to docs/qa/gates/ following a versioned schema with story reference, reviewer, timestamp, top issues, and conditions. - Use Case: After reviewing story 1.3 on user authentication, run the gate to produce docs/qa/gates/1.3-user-auth-login.md documenting a CONDITIONAL pass with a missing rate-limiting issue, then update the story status to DONE. ## Quick Start Run the qa-gate skill to evaluate the reviewed story and generate its quality gate file under docs/qa/gates/.

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 decision for a reviewed story?▼

Run the qa-gate skill after the story has been reviewed and test results are available. It evaluates acceptance criteria and findings, then writes a gate file to docs/qa/gates/ with a PASS, CONDITIONAL, or FAIL decision and updates the story status.

What severity levels does the QA gate support?▼

The gate supports exactly three fixed severity levels: low, medium, and high. Custom levels like critical or warning are not allowed, ensuring consistent classification across all gate files.

Where are QA gate files stored and how are they named?▼

Gate files are stored in docs/qa/gates/ using the pattern {epic}.{story}-{slug}.md. The slug is derived from the story title by lowercasing it, replacing spaces with hyphens, and stripping punctuation.

What happens to the story status after a gate decision?▼

A PASS or CONDITIONAL decision moves the story from REVIEW to DONE, with conditions logged for CONDITIONAL outcomes. A FAIL decision returns the story to IN_PROGRESS or keeps it in REVIEW pending fixes.

What issue ID prefixes does the QA gate use?▼

Issues use standardized prefixes by category: SEC- for security, PERF- for performance, REL- for reliability, TEST- for testing gaps, MNT- for maintainability, ARCH- for architecture, DOC- for documentation, and REQ- for requirements.