Open Prompts
Submit a prompt
Coding

PR Summary for Reviewers

Turns a raw diff and a short context note into a PR description reviewers can actually use, grounded in the real file and function names pulled from the diff rather than generic phrasing. Outputs a three-bullet what/why/risk summary, testing notes, the files that most deserve attention, migration or compatibility concerns, and a suggested PR title — and says so if the diff is too large to summarize well.

Prompt
You are a senior engineer writing a PR summary.

Summarize this diff.

Diff:
{{diff}}

Context:
{{context}}

Create:
1. Three-bullet summary:
   - What changed.
   - Why it changed.
   - What could go wrong.
2. Testing notes.
3. Files that deserve reviewer attention.
4. Migration or compatibility notes.
5. Suggested PR title.

Rules:
- Be concrete.
- Mention real file names and functions when visible.
- Do not use marketing language.
- If the PR is too large, say so.
Download .md

Variables

Related prompts

Coding

AI First-Pass Code Review

Paste a diff or code block and get a senior-engineer-style first pass before it reaches a human reviewer. - Flags bugs, security risks, performance issues, and maintainability problems - Rates each finding Critical, High, Medium, or Low with line references and a fix - Add project conventions (e.g. "no nested ifs") for sharper, more relevant results - Run it on every PR so reviewers only spend time on what's left after the obvious stuff is caught

Coding

Balanced Senior Engineer PR Review

Give it the PR's stated goal and your repo's architecture and conventions to get a review that avoids both rubber-stamping and nitpicking. It checks correctness, readability, maintainability, test coverage, and backward compatibility in one pass, then sorts findings into Confirmed Issues, Possible Risks, and Nice-to-Haves, closing with three ready-to-paste GitHub review comments.

Coding

Constructive Review Comment Writer

Describe the issue you've spotted in plain English along with the specific lines and fuller details, and get back a ready-to-paste GitHub review comment instead of staring at a blank comment box. The output is specific, explains why the issue matters, includes a concrete suggested fix, and skips filler openers like "Great work, but..." — also useful as a template for junior reviewers learning to write good comments.