qa-review

Validate code against story acceptance criteria, project rules, and regression risks.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill qa-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-review
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/delivery/qa-review
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill qa-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a critical quality gate, ensuring that implemented code fully meets acceptance criteria, adheres to established rules, and introduces no regressions before delivery.

Core Features & Use Cases

  • Acceptance Criteria Validation: Verifies that all defined acceptance criteria from a Story are demonstrably met in the code.
  • Scope and Rule Compliance: Checks that only intended files were modified and that all project rules are followed.
  • Regression Prevention: Scans for broken tests, behavior drift, and known risk patterns.
  • Use Case: After a developer completes a new feature, this Skill is activated to perform a final, rigorous check, guaranteeing that the code is production-ready and meets all quality standards.

Quick Start

Activate the qa-review skill to validate the implementation of story E01S01 against its acceptance criteria and project rules.

Frequently Asked Questions about qa-review

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

FAQPage Schema
How do I validate code against story acceptance criteria before deployment?

To validate code against story acceptance criteria, you need a quality gate that checks implementation completeness, project rule compliance, and regression risks. This ensures code meets all defined standards before delivery. It requires access to story definitions, the codebase, and historical bug memory.

What is a mandatory quality gate in the software delivery lifecycle?

A mandatory quality gate is a checkpoint that validates code implementation against acceptance criteria, project rules, and regression risks before deployment. It ensures only production-ready code that meets all quality standards is delivered.

How do I prevent regressions when implementing new features?

To prevent regressions when implementing new features, scan for broken tests, behavior drift, and known risk patterns using historical bug memory. This verifies code modifications introduce no unintended side effects before delivery.

How do I check scope compliance to ensure only intended files were modified?

To check scope compliance, validate the code implementation against project rules to verify only intended files were modified. This ensures the delivery strictly adheres to established constraints and prevents unauthorized changes.

Do I need historical bug memory to perform a regression risk scan?

Yes, historical memory of bugs and risks is required to effectively scan for behavior drift and known risk patterns. Accessing this history allows the quality gate to accurately prevent regressions before deployment.