qa-gate

Coordinate automated QA testing with tiered validation and pass/fail reporting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA gate ensures independent QA checks before delivering features, testing end-to-end to catch bugs before users see them.

Core Features & Use Cases

  • Tiered QA protocol with automatic subagent assignment for complex changes
  • Inline verification for small changes and quick sanity tests
  • Formal test checklists, pass/fail reporting, and rollback readiness

Quick Start

Dispatch a Tier 3 QA gate subagent to validate a new feature across its full end-to-end flow.

Frequently Asked Questions about qa-gate

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

FAQPage Schema
How do I automate end-to-end QA testing before shipping a feature?

Automated end-to-end QA testing before shipping is handled by dispatching an independent QA subagent to validate the full feature flow. It applies a structured protocol with a tiered test scope, runbook checklist, and formal pass/fail reporting.

When do I need to dispatch a QA subagent for feature verification?

Dispatch a QA subagent for feature verification when non-trivial changes require Tier 3 validation. Complex feature rollouts, bug fixes, and configuration changes trigger this independent testing, while small edits use inline verification instead.

What is a tiered QA protocol for automated bug catching?

A tiered QA protocol assigns different validation depths based on change complexity. Small edits receive inline verification for quick sanity tests, whereas complex rollouts trigger an independent Tier 3 subagent for full end-to-end bug catching.

Does the QA gate handle rollback readiness and reporting?

The QA gate handles rollback readiness and reporting by fulfilling a structured protocol. It provides formal test checklists, clear pass/fail reporting formats, and verifies rollback readiness before features are delivered.

Can I use inline verification for small configuration changes?

You can use inline verification for small configuration changes and quick sanity tests. The QA gate automatically applies this lightweight check instead of dispatching a full Tier 3 subagent for non-trivial edits.