Create structured pull requests following engineering best practices

Creates pull requests following Sentry's engineering practices: verify the branch state (detect the default branch, confirm all changes are committed and rebased), analyze the full diff and commit log against that base branch, write a PR description in a fixed four-part structure (what the PR does, why, alternatives considered, additional reviewer context) while deliberately omitting test-plan sections, checkbox testing lists, and redundant diff summaries, then open the PR as a draft with a conventional-commit-style title such as feat(scope): ..., fix(scope): ..., or ref: ....

Use it when ready to open a pull request and wanting a structured description generated from the committed branch diff rather than written ad hoc, especially when using GitHub CLI and wanting a repeatable PR-writing workflow. Requires the GitHub CLI (gh) authenticated and available. Before creating a PR, ensure everything is committed - if git status --porcelain shows uncommitted changes, run a commit skill first rather than proceeding. Guidelines: one PR per feature or fix (don't bundle unrelated changes), keep PRs small enough to review quickly, explain the why rather than restating what the diff already shows, and mark early work-in-progress PRs as drafts. It is not a substitute for environment-specific validation, testing, or expert review.

Inputs are the current branch's commit history and diff against the repository's detected default branch, found with:

gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'

Output is a created draft PR:

gh pr create --draft --title "<type>(<scope>): <description>" --body "$(cat <<'EOF'
<description body here>
EOF
)"

Issue references follow a fixed syntax - Fixes #1234 closes a GitHub issue on merge, Fixes SENTRY-1234 closes a Sentry issue, Refs GH-1234 links without closing, and Refs LINEAR-ABC-123 links a Linear issue. To edit an existing PR afterward, the skill uses gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER rather than gh pr edit, which it notes is currently broken due to GitHub's Projects (classic) deprecation.

Built on the GitHub CLI (gh) - gh repo view, gh pr create, and gh api for PATCH-based edits - plus git status, git log, and git diff for change analysis. It cross-references Sentry issues, GitHub issues, and Linear issues by their respective syntaxes, and follows the practices documented in Sentry's public engineering guidelines for code review and commit messages.

Engineers who want a repeatable, review-friendly way to open pull requests via GitHub CLI - one that captures what changed and why instead of a redundant diff summary, and enforces small, single-purpose, draft-first PRs.