Skip to content

DirectoryPrompts

Claude Opus 5.5

Write a PR Description – Pull request description prompt for ChatGPT and Claude

Freewith a Recaply account
  • Free with an account
  • Copy filled in or download
  • Updates included
votes views

Claude Opus 5.5

This prompt writes your pull request description. Paste your notes, your team's template and the diff; you get a title, a description ready to paste and the issues a reviewer would send back.

What you get

  • A short pull request title in the imperative
  • A description in your team's template, ready to paste, with placeholders for facts you did not give
  • Where a reviewer should look first and what is risky
  • A self-review list of leftover debug code, unrelated changes and missing tests, each with file and line

How to use it

  1. 1
    Paste notes, template and diff

    Write why you made the change and how you tested it, add your team's template or "none", then paste the diff.

  2. 2
    Clear the review list

    Fix the "Before you request review" items, or say in the description why you kept them.

  3. 3
    Fill the placeholders and open it

    Replace every placeholder with a real link or result, tick only the checklist items that are true, then paste the description.

Better results

  • Say how you tested in your notes, even briefly. The prompt only claims tests you mention, so a blank leaves a placeholder that reviewers will ask about.
  • Run it again after you clear the review list, so the description matches the final diff.
  • For a large change, paste the key files and a list of the rest, and ask for a "Where to start" line for reviewers.

Questions

How do I self-review a pull request?

Read your own diff as a reviewer would: look for leftover debug code, unrelated changes, missing tests and template items you skipped. This prompt runs that pass for you and lists each problem with its file, line and fix, next to the description it writes.

Can AI write pull request descriptions?

Yes. AI writes clear pull request descriptions from a diff and a few notes on why you made the change. It can only describe what the diff shows, so give it the reason, the ticket and how you tested, or it leaves placeholders for you to fill.

What makes a good pull request description?

A good pull request description says what changed, why, how to test it and what could go wrong, in a form a reviewer reads in under a minute. It points to where to start reviewing and links the ticket, without repeating every line of the diff.

Updated 6 Oct 2026

Reviews

No reviews yet
Reviews open soonThey will come only from signed-in people who used this prompt.

Similar prompts

More coding prompts

Image prompts

Video prompts

Trending prompts

Newest prompts

Browse all prompts