review-pull-request-qa
Installation
SKILL.md
Goal
Assess a pull request in a representative full local or preview environment and return a reproducible QA report without changing product code or deciding whether to merge.
Definition of Done
- The PR candidate, base, connected service revisions, target environment, test authority, and acceptance criteria are identified.
- Environment readiness and any isolated test-data setup are observed; unavailable or unsafe prerequisites remain explicit gaps.
- Required checks and risk-selected backend, frontend, and cross-layer journeys have actual outcomes or named coverage gaps, including relevant regressions.
- Visual and diagnostic claims cite valid screenshots, logs, or other observed evidence rather than inferred success.
- The report separates case results from the candidate-and-environment QA verdict, defects, exclusions, and residual risk; report acceptance does not certify an untested target.
Boundaries
- Tests may write only authorized, isolated, resettable test data. Never run a seed against production or an ambiguous shared target; continue safe independent checks and request a consequential decision only if the remaining required test cannot be isolated.
- Do not repair product code, deploy, approve, or merge. A completed assessment with gaps does not certify the PR or claim that all regressions are absent.