qa-review

Name: qa-review
Availability: InStock
Author: petrsimonidesxart

Validate story acceptance criteria against the implemented codebase and generate a PASS/FAIL qa_report.

Updated Mar 8, 2026

Search Tags:#quality-gate #acceptance-criteria #regression-testing #qa-review #story-traceability

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill qa-review-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-review
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/delivery/qa-review
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill qa-review-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that code changes fully satisfy story acceptance criteria, enforces compliance with rules, and prevents regressions from shipping.

Core Features & Use Cases

Automated acceptance-criteria conformance checks against the implemented codebase.
Scope and rule integrity validation with regression risk assessment.
Generates a structured qa_report mapping results to story identifiers for traceability.

Quick Start

Activate the QA Review against the latest code changes to produce a PASS/FAIL qa_report with per-criterion evidence.

Frequently Asked Questions about qa-review

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

FAQPage Schema

How do I validate Story acceptance criteria against an implemented codebase?▼

To validate Story acceptance criteria against an implemented codebase, a QA review checks the working tree and artefact contexts to detect regressions, scope creep, and rule violations, producing a PASS or FAIL report with per-criterion evidence.

What is automated acceptance-criteria conformance checking and how does it work?▼

Automated acceptance-criteria conformance checking compares implemented code changes against defined Story requirements to determine conformance. It applies to working tree and artefact scopes to detect regressions, scope creep, and rule violations.

How do I enforce a hard quality gate to prevent regressions from shipping?▼

Enforcing a hard quality gate to prevent regressions involves validating code changes against Story acceptance criteria and rule contexts. This generates a structured qa_report with PASS or FAIL results and per-criterion evidence for traceability.

Can I generate a QA report mapping regression test results to story identifiers?▼

Yes, you can generate a QA report mapping regression test results to story identifiers. The review validates acceptance criteria and links results to corresponding story identifiers, producing a structured qa_report with PASS or FAIL and per-criterion evidence.

What is the best way to detect scope creep and rule violations in working tree artefacts?▼

The best way to detect scope creep and rule violations in working tree artefacts is to run an automated QA review against the latest code changes. It validates rule integrity and generates a qa_report mapping any failures to story identifiers.