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 declared risk scope.
• route to another skill when the requested action is outside this skill's owner boundary.

You MUST:

• inspect before acting.
• keep the task within the declared owner boundary.
• classify state and risk before any meaningful action.
• preserve unrelated user work.
• verify outcomes proportional to risk.
• report evidence, assumptions, actions, verification, and residual risk.

You MUST NOT:

• invent project policy.
• expose secrets or sensitive values.
• mutate unrelated files or refs.
• perform destructive, remote, shared, history-rewriting, or irreversible actions without explicit action-specific confirmation.
• continue after unexpected destructive output.

State / Risk Table

Workflow

1. Identify the user goal and current owner boundary.
2. Inspect required evidence.
3. Classify repository/task state.
4. Classify risk using the declared scope.
5. Choose the minimal sufficient action or route.
6. Execute only allowed actions, if any.
7. Verify outcome or self-check the artifact.
8. Report result, evidence, verification, assumptions, and residual risk.

Decision Rules

• Separate facts from inferred reviewer guidance.
• Do not claim tests passed unless evidence exists.
• Flag security/data/migration/public API areas as reviewer focus, not as verified safe.
• Do not create or update remote PRs.

Tool Rules

• May inspect diffs, logs, templates, and test config.
• May write a local PR body file only if explicitly requested.
• Must not push or call hosting APIs.

Verification

Minimum verification:

• Check PR summary covers all major change areas.
• Verify reviewer focus maps to actual files or evidence.
• Report verification performed and not performed.

Risk-based floor:

• R0-R1: evidence inspected and output self-checked.
• R2: inspect resulting diff or local state.
• R3: verify local state and report recovery limits.
• R4-R5: require explicit confirmation, preflight evidence, and post-action verification where this skill owns the action.

Output Contract

Final response must include:

## Result

- Decision, action, or artifact produced.

## Evidence

- Files, commands, diffs, refs, or assumptions used.

## Verification

- Checks performed and their result.

## Risks / Limitations

- Remaining uncertainty, blocked actions, or routed next steps.

Stop / Confirmation Rules

Stop when the repository state is dirty, conflicted, diverged, missing required evidence, or ambiguous in a way that could overwrite user work, invalidate the requested scope, or require a gated action.

Require explicit action-specific confirmation for:

• destructive local mutation.
• remote/shared mutation.
• history rewriting.
• security/secret/data impact.
• irreversible or hard-to-recover operation.

Broad approval such as "do whatever" is not enough for R4-R5 actions.

Lazy-load References

Load references/pr-body.md when:

• the task needs the detailed guidance described by the file name.
• the state/risk table identifies an ambiguous or high-risk path.

Load references/reviewer-focus.md when:

• the task needs the detailed guidance described by the file name.
• the state/risk table identifies an ambiguous or high-risk path.

Load references/risk-signals.md when:

• the task needs the detailed guidance described by the file name.
• the state/risk table identifies an ambiguous or high-risk path.