What problem does it solve? Writing a good pull request means re-reading your own branch, summarizing commits, filling in the PR template, and remembering to push, sync, and update the linked issue. This Skill automates that entire flow so the PR title, body, and test plan come from the actual commits and diff rather than from memory. ## Core Features & Use Cases - PR drafting from real changes: Generates a Conventional Commits-style title, summary, changes list, and test plan from the branch's commits and diff, filling in the repo's pull request template when one exists. - Full lifecycle handling: Syncs the branch with the base via rebase, pushes with force-with-lease when needed, creates or updates the PR with gh pr create/gh pr edit, and supports stacked PRs with correct per-layer bases. - Workflow integration: Embeds verifykit proof artifacts, flips the linked issue's label from in-progress to in-review, and moves dependent issues from blocked to stacked. - Use Case: After finishing a feature branch, ask the agent to open a PR; it fetches the base, writes the title and body from your commits, pushes the branch, creates the PR with the gh CLI, and hands off the PR URL. ## Quick Start Ask the agent to open a pull request for the current branch and it will draft the title and body from your commits, push the branch, and create the PR with the gh CLI.