pr-review-preplisted

# PR Review Prep ## Core Question What changed in this branch, what should reviewers focus on, and what verification or risks should be disclosed? ## When To Use Use this skill when: - the user wants a PR description or review-ready summary - the branch diff needs risk and reviewer focus areas - the user wants tests performed/recommended summarized - the user wants a local PR body draft ## When Not To Use Do not use this skill when: - deciding whether to merge - creating a PR remotely - pushing a branch - rewriting branch history - publishing releases Route to: - merge gate decisions route to `merge-readiness` - commit range selection routes to `commit-range-select` if added later or `repo-state-diagnosis` - release notes route to `release-notes` - changelog updates route to `changelog-maintenance` ## Required Evidence Before action, inspect or establish: - target branch or merge-base - changed file list and diff summary - notable implementation diffs - test/build/lint evidence - security, data, migration, release, or public API indicators - existing PR template if present No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - inspect relevant repository state and project files. - generate a plan, report, or local artifact within the declare