qa-pr-requirements-analyzer
QA PR Requirements Analyzer
Find the linked requirement, resolve relevant decisions, and extract what the PR is expected to deliver.
This skill supplies documented intent to qa-review-pr. It does not assess implementation, identify risks, generate test scenarios, or invent acceptance criteria.
1. Find linked requirements
-
Accept a PR URL or number, or use the current branch's PR when available. If neither is identifiable, ask for the PR reference.
-
Read the PR title, description, and relevant discussion to find issue references and the stated relationship to them. Check explicit linked issues and ticket references in the branch name where available.
-
Resolve references with the available authorized tracker tools. Read the actual issues; a reference alone is not requirement content.
-
Do not inspect diffs, changed files, or commits to reconstruct intent.
-
If there is no linked issue, output exactly this and stop:
No linked requirement found. Requirements extraction skipped.
-
If a linked issue exists but cannot be read, name the inaccessible source and state that extraction is blocked for that source. Continue with other accessible linked requirements. Do not treat inaccessible requirements as absent or substitute code-derived behavior.