create-pr

Create PR

1. Identify the current branch and an appropriate base branch. Inspect the intended changes, including uncommitted work, and use the conversation context already available. Check claims against the actual branch rather than relying on memory. Preserve file contents, unrelated changes, and unrelated staging.
2. Write the title and description in the current session using the guidance below.
3. Read the description as a teammate about to review the diff. Keep the outcome and useful heads-ups; cut implementation narration and explanations already present in the changed code or documents.
4. If asked only for a description, return the title and body without changing Git state or creating a PR. Otherwise, prepare the PR branch locally, creating one if needed. Commit only the intended changes if needed, then push that branch. Keep the local checkout on the PR branch.
5. Create the PR as a draft unless explicitly requested ready for review. Confirm the published body matches the intended text. Return the URL, or the title, body, and blocker if preparation or creation fails.

Description

Write from the PR author's perspective, not as an assistant reporting on their work.

Tell a teammate what this makes possible, and why now if they'd ask. Assume they'll read the diff. Most PRs need only a short sentence describing the outcome. Then name only what a reviewer must decide or do before merging, such as a merge or deploy order. Keep discussion tied to a particular line in an inline comment rather than the description.

Answer what a reviewer, or someone tracing this change later, would ask first: how do you know it works? Show what you would show a teammate at your desk, beside the claim it backs, and let it replace the explanation where possible. Reuse it from the session or capture it now; gh pr create --help covers --attach. Tests and CI show that logic meets a contract, not that the change works in practice; leave out that they pass.

Fold every other note into one <details> block after the evidence, with a <summary> that says what it holds and a blank line after </summary>.

End the body with a line for each issue the PR references. Read its open acceptance criteria: write Closes #N when this PR meets the last of them, and Refs #N otherwise.