Make PR

Overview

Use this skill to draft and open a PR with consistent, high-signal writing. Keep headings sparse and focus on the problem/feature explanation, context links, and practical code examples. Optimize for the shortest path to a credible PR, not the fullest possible context-gathering pass.

Workflow

1. Check the fast-path blockers first.

• Check git status --short --branch and git branch --show-current before doing deeper prep.
• If the repo is in a detached HEAD or worktree state and the user wants a PR opened, create a branch early.

1. Gather only the context needed to write the PR.

• Capture what changed, why it changed, and who it affects.
• Find related issues/PRs and include links when relevant.
• Prefer git diff --stat plus the relevant diff over broad repo archaeology when the change is small.
• If the user supplies a report, issue, or related PR, treat that as the primary context source.