qa-gate

Automate quality gate creation and persist results as YAML.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/michael-menard/monorepo --skill qa-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-gate
Source: https://github.com/michael-menard/monorepo/tree/main/.claude/skills/qa-gate
Command: npx skills add https://github.com/michael-menard/monorepo --skill qa-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation and maintenance of quality gates for code changes and stories.

Core Features & Use Cases

  • Automated quality gate generation with persistent YAML output for traceability.
  • Supports standard gate statuses (PASS, CONCERNS, FAIL, WAIVED) and waivers with approval tracking.
  • Integrates automated checks and optional specialist reviews, and updates related story references.

Quick Start

Quick-start commands:

  • /qa-gate 3.1.5 (runs tests, types, lint)
  • /qa-gate 3.1.5 --deep
  • /qa-gate --branch
  • /qa-gate 3.1.5 --security --performance
  • /qa-gate 3.1.5 --waive --reason "MVP release" --approved-by "Tech Lead"
  • /qa-gate 3.1.5 --dry-run

Frequently Asked Questions about qa-gate

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

FAQPage Schema
How do I automate quality gates for code changes in CI/CD pipelines?

Automating quality gates involves orchestrating automated checks and optional specialist reviews, then persisting results as YAML to track PASS, CONCERNS, FAIL, or WAIVED statuses across branches and releases.

What is the best way to track quality gate waivers with approval metadata?

Tracking quality gate waivers requires persisting the waiver reason and approver metadata in YAML output, ensuring traceability and standardized gate enforcement across the development lifecycle.

How do I run specialized security and performance checks during code review?

Specialized security and performance checks are triggered using specific command flags during the quality gate process, executing targeted NFR validation alongside standard automated test, type, and lint checks.

Can I execute a dry-run of quality gate checks before applying them to a branch?

Yes, executing a dry-run of quality gate checks evaluates automated tests and linting without persisting final statuses, allowing you to preview results before committing gate outcomes to YAML.

Does this quality gate automation tool support deep specialist reviews?

Yes, deep specialist reviews are supported by invoking specific command flags, which orchestates comprehensive automated checks and optional expert evaluations with detailed metadata tracking.

How do I enforce a standardized quality gate model across multiple software releases?

Enforcing a standardized quality gate model requires persisting gate results as YAML with strict statuses and reviewer metadata, ensuring traceability and consistent validation across branches and releases.