Creating Pull Requests

Prepare a PR from the current branch, show a preview, and open it only after explicit approval.

Rules

• Inspect the real branch changes before drafting the PR.
• Always show the title and body preview before pushing or opening the PR.
• Never push or create a PR without explicit approval.
• If Features or Fixes has no real items, write N/A.
• Link relevant GitHub issues using GitHub's supported reference syntax.
• Use closing keywords only when the user intends that state change.
• For a release PR, use the title Release only when the repository convention requires it.
• Never target a release branch unless the user explicitly asks for a release PR.
• For a release PR, verify the expected head branch from repository convention; ask before continuing if it does not match.

Workflow

Copy this checklist and track progress: