Ask Claude to Draft a Pull Request Description from Your Branch Changes
Writing PR descriptions is the task everyone skips or rushes. Claude reads your actual branch changes and writes one that helps reviewers understand what they're approving.
"Read the commits on this branch compared to main and write a PR description"
Claude runs git log and git diff against your base branch, reads the changed files, understands the purpose of each change, and writes a structured description:
## Summary
Add email verification requirement to user registration flow.
## Changes
- Added `verified_at` column to users table
- Created verification email notification
- Added middleware to block unverified users from protected routes
- Updated registration controller to send verification email
- Added verification endpoint and success page
## Why
Users were signing up with invalid emails, causing delivery failures
for order confirmations and password resets.
## Testing
- Register a new user and check for verification email
- Try accessing /dashboard before verifying — should redirect
- Verify the email and confirm dashboard access works
You can customize the format:
# Match your team's PR template
"Write a PR description following our template in .github/pull_request_template.md"
# Include technical details for complex changes
"Write a detailed PR description explaining the architectural decisions"
# Keep it short for small changes
"Write a brief one-paragraph PR description for this bug fix"
# Create the PR directly
"Read my branch, write a PR description, and create the PR on GitHub"
Claude can also open the PR for you if you use the GitHub CLI:
"Create a PR from this branch to main with a proper title and description"
Claude writes the title, description, and runs gh pr create — your PR is open and documented in one prompt.
For the best descriptions, Claude reads not just the diff but the commit messages, so writing good commits pays double when it's time to describe the PR.
Good PR descriptions get fast reviews. Let Claude write the description while the changes are fresh — not after you've forgotten the details.
via Claude Code
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.