What it does
Assesses whether a change is safe and well-tested: maps the diff to risk areas, checks coverage of the changed code, scopes regression, reviews added tests, and files real defects — without editing the PR's product code.
When to use it
Before merging a PR, when you want the testing view (not a code-style review).
Prerequisites
qa.config.yml (tooling, paths, gates, risk_areas); the gh CLI or a local git diff vs the base branch.
Output
ISO/IEC/IEEE 29119-3 Review Report -> reports/PR-REVIEW-<id>-<date>.md, plus a merge recommendation.
Mechanics
How it works
- Resolve the change set (gh PR or local diff vs base)
- Map changed areas to risk_areas tiers
- Assess coverage of changed files; count uncovered
- Scope regression and hand to /qa:regression
- Review added testware for anti-patterns
- File real defects via /qa:triage (no code edits)
- Evaluate gates -> Approve / Conditions / Request changes / Block
Why it works
The theory behind it
A test-focused static review of a change set (CTFL §3) plus impact analysis (§2.3) and risk-based depth (§5.2). Reviews remove defects before execution, the cheapest point (Principle 3); real defects escalate via triage, never hidden (Principle 1).
CTFL v4.0 §3 · §2.3 · §5.2 · CTAL-TA
Example
See it in use
> /qa:review-pr 482✓ Correct when It maps the diff to risk_areas, reports coverage as counts, scopes regression, files real defects via triage, and the merge call names the gates item that drives it.
Related commands
Used by