qa-review

Validate implemented code against story acceptance criteria and project rules.

157|28|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Fr-e-d/GAAI-framework --skill qa-review-fr-e-d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-review
Source: https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/delivery/qa-review
Command: npx skills add https://github.com/Fr-e-d/GAAI-framework --skill qa-review-fr-e-d

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 meets all defined acceptance criteria, adheres to project rules, and does not introduce regressions before delivery.

Core Features & Use Cases

  • Acceptance Criteria Validation: Verifies that every acceptance criterion for a story is demonstrably met in the code.
  • Scope Integrity: Confirms that only the intended files and features were modified, preventing scope creep.
  • Rule Enforcement: Checks for compliance with project-specific coding standards and rules.
  • Regression Detection: Scans for broken tests, behavioral drift, and known risk patterns.
  • Use Case: After an AI has implemented a new feature, this Skill rigorously checks the changes against the story's requirements and project standards, preventing faulty code from being merged.

Quick Start

Run 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 acceptance criteria before a merge?

Code validation against acceptance criteria requires verifying that implemented changes demonstrably meet every story requirement, project ruleset, and regression risk pattern. This quality gate process ensures only compliant code reaches the merge stage.

How does regression detection work during code review?

Regression detection during code review scans implemented changes for broken tests, behavioral drift, and known risk patterns. It leverages optional memory of past issues alongside codebase analysis to prevent faulty code from being merged.

Can I check for scope creep and rule enforcement in an automated delivery pipeline?

Yes, scope integrity checks confirm only intended files and features were modified to prevent scope creep. Rule enforcement simultaneously verifies compliance with project-specific coding standards within the delivery pipeline before merge.

Do I need story artifacts and rulesets to run a quality gate check?

Yes, comprehensive quality assurance requires access to story artifacts, the codebase, and rulesets. Optional memory of past issues can also be provided to ensure thorough regression detection and scope validation.

What is the best way to prevent faulty AI-generated code from being merged?

The best way to prevent faulty AI-generated code from merging is applying a rigorous quality gate that validates implementation against story acceptance criteria and project standards. This confirms scope integrity and detects regressions before delivery.