| name | pr |
| description | Open a pull request with a clear description, test plan, and reviewer checklist, grounded in the actual branch diff. Use when the user asks to open, create, or raise a PR. |
pr
Open a pull request a reviewer can approve with confidence: it explains what
changed and why, and shows the change was verified.
Steps
- Confirm the branch state.
- Current branch and its base:
git status, git branch --show-current.
- If on the default branch, stop and create a feature branch first.
- Read the full diff against the base:
git diff <base>...HEAD.
- Ensure commits are pushed:
git push -u origin HEAD.
- Write the description from the diff, not from intentions:
- What & why: the problem and the chosen solution, in a few sentences.
- Changes: the notable changes as a short bulleted list.
- Test plan: the exact commands/steps run to verify, with their outcome.
- Risk / rollout: anything risky, breaking, or needing follow-up.
- Link issues the user references (
Closes #123).
- Create the PR with the
gh CLI:
gh pr create --title "<title>" --body "<body>" (use a heredoc for the body).
- Report the PR URL.
Checklist before opening
Rules
- Describe only what the diff contains; do not claim tests you did not run.
- Keep the description skimmable: a reviewer should grasp the change in 30 seconds.
- Do not push to the default branch or force-push a shared branch.
- Confirm before opening if the user has not clearly authorized creating the PR.
