Pull Request Summary

The Problem

Writing good PR descriptions is tedious but critical. Reviewers skip PRs with empty descriptions, vague titles lead to confusion in git history, and missing test plans mean nobody knows how to verify the change. You’ve already written the code — the AI can analyze the diff and generate a professional PR summary in seconds.

The Prompt

Generate a professional pull request description from the following diff. The output should be ready to paste into GitHub/GitLab.

DIFF:
[paste your git diff here — use `git diff main` or `git diff --staged`]

CONTEXT (optional):
- Related issue: [e.g., #142, JIRA-456]
- Why this change: [brief reason if not obvious from the diff]

Generate:
1. **PR Title**: Under 70 characters, action-oriented (e.g., "Fix race condition in user auth flow")
2. **Summary**: 3-5 bullet points explaining WHAT changed and WHY
3. **Changes**: List of files changed with one-line explanation each
4. **Test Plan**: How a reviewer should verify this works
5. **Breaking Changes**: Any backwards-incompatible changes (or "None")
6. **Screenshots**: Note if screenshots would be helpful (e.g., for UI changes)

Example Output

## Fix null pointer in checkout flow when cart is empty

### Summary
- Handle edge case where user reaches checkout with an empty cart
- Add guard clause in `calculateTotal()` to return 0 for empty arrays
- Add unit test covering the empty cart scenario

### Changes
- `src/checkout/calculateTotal.ts` — Add early return for empty cart
- `src/checkout/__tests__/calculateTotal.test.ts` — Add empty cart test case

### Test Plan
- [ ] Run `npm test` — all tests pass
- [ ] Navigate to /checkout with empty cart — should show "Cart is empty" message
- [ ] Add items and checkout normally — existing flow unchanged

### Breaking Changes
None

When to Use

Use this every time you open a pull request. Paste your git diff output and get a complete description in seconds. Especially valuable for large PRs where summarizing changes manually would take 10+ minutes, and for teams that require structured PR templates.

Pro Tips

• Pipe directly from git — run git diff main | pbcopy (macOS) to copy your diff to clipboard, then paste into the prompt.
• Include your team’s PR template — add “Follow this template: [paste template]” to get output that matches your team’s format exactly.
• For stacked PRs, add context about what the previous PR did so the summary explains how this PR builds on it.