draft-prlisted

# draft-pr Produce a **ready-to-paste PR draft** (title + Markdown body). This skill NEVER creates, pushes, or opens a PR. It does not run `gh pr create`, does not push branches, does not open compare URLs. Output only — the PR is the user's to open. ## Input (any of) - Nothing → use the current change (`git diff` on the current branch vs base). - An issue link / id → read it for context on *what's wrong*, pair with the current diff. - A compare/PR link → base the draft on that diff. - A pasted diff or plain description → draft from that. ## The repo outranks this file Before drafting, look for what the project already requires and follow that instead of the defaults below: - **A PR template** — `.github/PULL_REQUEST_TEMPLATE.md`, a `PULL_REQUEST_TEMPLATE/` directory, `.gitlab/merge_request_templates/`, or one linked from the contributing docs. Fill its sections as written and keep its headings and checklists, even where they differ from the shape below. - **Written rules** — `CONTRIBUTING.md`, `CLAUDE.md`, `AGENTS.md`: title conventions, a required issue link, required trailers or sign-off, labels, conventional-commit titles. - **What actually gets merged** — `gh pr list --state merged --limit 5 --json title,body`. Real practice beats a stale written rule. Where the repo is silent, use the style below. Where it conflicts, the repo wins. Two rules hold either way: **never touch a remote**, and **never sign the draft as AI-authored**. ## Steps 1. **Locate the repo.**