What it does
Builds a change-level test summary from the branch diff — what changed mapped to risk areas, what was tested with counts, the regression scope, residual risk, and linked defects — then opens the PR via the gh CLI on confirmation.
When to use it
When raising a PR and you want the QA evidence attached for reviewers to trust.
Prerequisites
qa.config.yml (tooling, paths, risk_areas, gates); a pushed branch; the gh CLI to open the PR (else outputs the body for manual creation).
Output
Change-level ISO/IEC/IEEE 29119-3 Test Completion-style summary -> reports/PR-<head>-<date>.md, used as the PR body; the PR URL.
Mechanics
How it works
- Resolve base + head; confirm the branch is pushed (only on confirmation)
- Summarize what changed and why, areas mapped to risk_areas
- State what was tested — levels/suites, coverage delta, regression set
- State residual risk and link defects/tickets
- Assemble the PR body from the completion-report template
- Open the PR via gh on confirmation (never force-push)
Why it works
The theory behind it
Test reporting at change scope — a completion-style summary (CTFL §1.4 completion; §5.3 reporting; ISO/IEC/IEEE 29119-3). It carries the evidence a reviewer needs and states residual risk (Principle 1) — a change-scoped echo of the Test Completion Report.
CTFL v4.0 §1.4 · §5.3 · ISO/IEC/IEEE 29119-3
Example
See it in use
> /qa:open-pr main✓ Correct when The PR body states what changed, what was tested (coverage delta, regression set) as counts, residual risk, and linked defects — and the PR is opened only on confirmation, never force-pushed.
Related commands
Used by