Writing PRs and commits

Use this skill when the user asks to create a PR, update an existing PR title or body, or write a commit message for a change that maps cleanly to one PR.

Resolve the target

• If the user names a PR number or URL, use that.
• Otherwise, inspect the current branch and use gh pr view --json number,title,body,baseRefName,headRefName,url to find the associated PR.
• If no PR exists and the user wants one created, use gh pr create, then immediately verify or adjust the title and body.
• If the user wants text only, provide the draft without mutating GitHub.
• When a PR is part of a stack, describe only the net change between the PR head and its base branch. Do not describe the full stack relative to main.

Core writing rules