qa-review

Review code changes for test coverage gaps, edge cases, and regression risks.

12.6k|1.5k|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/nearai/ironclaw --skill qa-review-nearai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-review
Source: https://github.com/nearai/ironclaw/tree/main/skills/qa-review
Command: npx skills add https://github.com/nearai/ironclaw --skill qa-review-nearai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify weak or missing automated tests by reviewing code changes for coverage gaps, edge cases, and regression risk before they reach production.

Core Features & Use Cases

  • Coverage analysis: Detects changed modules/functions without corresponding tests and evaluates whether existing tests assert meaningful behavior.
  • Edge case identification: Surfaces boundary, type, concurrency, state-transition, and external-failure scenarios that commonly fail in real deployments.
  • Regression risk assessment & test health tracking: Flags what existing behavior could break, and supports ongoing monitoring of coverage trends, flakiness rate, and time-to-test.

Quick Start

Run qa-review on your pull request or changed files to produce a structured QA review with coverage gaps, missing edge cases, regression risks, and a practical test plan.

Frequently Asked Questions about qa-review

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

FAQPage Schema
How do I find missing test coverage for code changes in a pull request?

To find missing test coverage, review changed modules and functions to identify paths lacking corresponding tests. This detects untested code changes and evaluates whether existing assertions validate meaningful behavior before deployment.

What is regression risk assessment and how does it prevent broken existing behavior?

Regression risk assessment identifies what existing behavior could break by analyzing modified code paths. It flags likely regression vectors before deployment, preventing degraded functionality from reaching production environments.

How do I identify overlooked edge cases in my test plan?

To identify overlooked edge cases, analyze boundary, type, concurrency, state-transition, and external-failure scenarios. This surfaces conditions that commonly fail in real deployments and generates concrete manual verification guidance.

Can I track test health metrics like flaky rate and coverage trend over time?

You can track test health metrics including coverage trends, flakiness rate, and time-to-test over time. This supports ongoing test-health check-ins to detect declining quality and ensure continuous regression readiness.

Does qa-review work for ongoing test health check-ins or only pull request QA?

It works for both pull request QA and ongoing test-health check-ins. The review fits regression readiness workflows and continuous monitoring scenarios where declining test quality is detected over time.