GitHub Release PR Writer

Write release pull request descriptions that help maintainers verify what will be released and why the release-preparation diff is correct.

Operating Boundaries

• Treat this skill as a specialized companion to a general PR workflow. Use the general PR skill for branch readiness, ordinary change descriptions, reviewers, and PR creation.
• Default to a local Markdown draft. Do not create or update a GitHub pull request unless the user explicitly asks for that write.
• Inspect URLs and GitHub state read-only when the user asks to review, assess, draft, or improve wording.
• Separate release-preparation changes from the product history being released.
• Use repository evidence instead of reconstructing a release solely from conversation memory, commit wording, or the files changed by the release PR.

Workflow

1. Discover repository and release conventions

Read applicable repository instructions, PR templates, release documentation, version manifests, and representative recent release pull requests.

Identify: