qa-review

Analyzes code changes to generate test plans and assess regression risk.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/zeropoint-foundation/ironclaw --skill qa-review-zeropoint-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-review
Source: https://github.com/zeropoint-foundation/ironclaw/tree/main/skills/qa-review
Command: npx skills add https://github.com/zeropoint-foundation/ironclaw --skill qa-review-zeropoint-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA review for code changes — test coverage analysis, edge case identification, test plan generation, regression detection, test health tracking over time.

Core Features & Use Cases

  • Covers changed code paths: Identify changed functions/modules and verify corresponding tests exist.
  • Edge-case discovery: Highlight boundary conditions and potential failure modes.
  • Plan generation: Produce structured test plans and regression risk assessments.
  • Review methodology: Provide a repeatable QA review workflow for PR readiness and weekly health checks.

Quick Start

Ask the QA reviewer to run the QA Review on a pull request to generate a test plan and risk assessment.

Frequently Asked Questions about qa-review

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

FAQPage Schema
How do I generate a test plan and regression risk assessment for a pull request?

To generate a test plan for a pull request, you can run a QA review on the code changes. This analyzes modified paths to enumerate edge cases, assess regression risk, and produce actionable testing guidelines.

What is the best way to identify edge cases and boundary conditions in changed code?

Identifying edge cases in changed code is done through a targeted QA review that highlights boundary conditions and potential failure modes. It scans modified functions and modules to pinpoint areas needing validation.

How can I check if my test coverage adequately matches my recent code changes?

You can check test coverage against recent code changes by analyzing modified functions and modules to verify corresponding tests exist. This coverage analysis identifies gaps where new paths lack validation.

Can I use this QA review methodology for sprint retrospectives and weekly health checks?

Yes, you can use this QA review methodology for sprint retrospectives and weekly test health checks. It provides a repeatable workflow to assess coverage, track edge cases, and monitor regression risk over time.

Does test coverage analysis automatically detect regression risk for new modifications?

Yes, test coverage analysis detects regression risk by mapping changed code paths against existing tests. It evaluates whether modifications introduce untested boundary conditions or failure modes that require new validation.