---
name: pull-request-writer
description: Create pull requests with well-structured descriptions by analyzing commits to generate summaries, change lists, and test instructions.
---

# Pull Request Writer

## 1. What it does
Analyzes a branch's commit history to draft a clear pull request description: change summary, list of affected files, and instructions for testing the feature. Makes code review easier for a team or technical client.

## 2. When to use it
- Finishing a feature and needing to open a pull request
- Needing to document complex changes for a reviewer
- Standardizing a team's PR format

## 3. Steps
1. Review the branch's commit history
2. Summarize the overall purpose of the change
3. List the affected files and modules
4. Write clear instructions for testing the change
5. Include risk or dependency notes if any exist
6. Present the final description before opening the pull request

## 4. GoHighLevel angle
If the change touches a GoHighLevel API integration, note in the description which endpoints or webhooks were affected.

## 5. Safety rules
Always work in draft mode: nothing is sent, published, or paid for without explicit client approval. Never invent data, metrics, or results. No passwords, tokens, or API keys are requested or shown in chat.

## 6. Deliverable
A clear, reviewable draft of the output (text, code, report, or file), ready for the user to approve before it becomes final.