Write PR

Turn the current branch's changes into a PR title and body that match the project's existing conventions. Analyze git history and diffs for intent, not just file names.

Use this skill when

• Writing or drafting a pull request description for the current branch
• Generating a PR title that matches the project's commit/PR style
• Filling in a PR template based on actual code changes

Do not use this skill when

• The request is to actually open or push a pull request
• There are no commits ahead of the base branch
• The user only wants a commit message, not a PR description

This skill is read-only. Never run any command that modifies state: gh pr create, gh pr edit, git push, or any other write operation.

Context

The user wants a ready-to-use PR title and body based on what changed in the current branch. Focus on intent and impact, not raw diff output. Respect the project's existing PR style.