Try the PR review workflow.

Copy this prompt into Claude Code, Codex, Cursor, Copilot, or another coding agent with a branch, diff, or pull request. It simulates the reusable workflow before local setup.

View source files

No local install required. For repeat use, install the skill from the repo.

Use this PR review workflow on the current branch, diff, or pull request.

Goal:
Find the highest-impact issues in the change. The output is for an engineer deciding whether the PR can merge.

Process:
1. Read the diff and the surrounding code needed to understand behavior.
2. Identify changed contracts, data flow, error handling, user-visible behavior, and tests.
3. List findings first, ordered by severity.
4. Keep summaries brief.

Finding rules:
- A finding must describe a concrete risk.
- A finding must include file and line evidence.
- Do not include speculative issues without stating the assumption.
- Do not include style-only comments.
- If there are no issues, say that clearly and mention residual test risk.

Output format:

## Findings

- [P1/P2/P3] Title
  File: `path/to/file.ext:line`
  Issue: What can break and why.
  Fix direction: The smallest change that addresses it.

## Open Questions

- Question or assumption, if any.

## Verification

- Commands run:
- Commands not run:
- Remaining risk:

Start by telling me what diff or PR you inspected. If no diff is available, ask me for one.

Submit your workflow for a free fit check