GPT-4o
💻 Coding & Dev
Intermediate
Pull Request Writer
Generate a complete, professional pull request description from code changes, commit history, or a feature brief.
The Prompt
# Pull Request Writer You are a senior software engineer and technical communicator. Write a comprehensive, professional pull request description based on the information provided below. **PR Context:** - PR Title: [PR_TITLE] - Repository: [REPO] - Author: [AUTHOR] - Base Branch: [BASE] | Head Branch: [HEAD] - Linked Issue / Ticket: [ISSUE] - What Was Changed (summary or paste your diff/commit messages): [CHANGES] --- ## Pull Request Description ### Summary A clear 2–4 sentence description of what this PR does and why. Written for a reviewer who has not seen the code. ### Motivation & Context - What problem does this PR solve? - Why is this the right approach? - Any design decisions or trade-offs made? ### Type of Change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactor (code change that neither fixes a bug nor adds a feature) - [ ] Performance improvement - [ ] Documentation update ### Changes Made A detailed breakdown of what was changed, added, or removed — organized by file or component: | Component / File | Change Type | Description | |-----------------|-------------|-------------| | [file] | Added/Modified/Deleted | [What and why] | ### Testing - **How was this tested?** (unit tests, integration tests, manual testing steps) - **Test environment:** (local, staging, specific browser/device) - **Test cases covered:** - [ ] [Test case 1] - [ ] [Test case 2] - **Edge cases considered:** ### Screenshots (if UI change) [Add before/after screenshots or describe UI changes] ### Checklist - [ ] Code follows project style guidelines - [ ] Self-review completed - [ ] Comments added for complex logic - [ ] Tests added and passing - [ ] Documentation updated - [ ] No breaking changes (or breaking changes documented) - [ ] Linked issue updated ### Notes for Reviewers Anything specific reviewers should focus on, known limitations, or follow-up work planned.
📝 Fill in the blanks
Replace these placeholders with your own content:
[PR_TITLE]
[REPO]
[AUTHOR]
[BASE]
[HEAD]
[ISSUE]
[CHANGES]
[ ]
[file]
[What and why]
[Test case 1]
[Test case 2]
[Add before/after screenshots or describe UI changes]
How to use this prompt
1
Copy the prompt
Click "Copy Prompt" above to copy the full prompt text to your clipboard.
2
Replace the placeholders
Swap out anything in [BRACKETS] with your specific details.
3
Paste into GPT-4o
Open your preferred AI assistant and paste the prompt to get started.