What problem does it solve? Writing pull request titles and bodies that communicate the approach behind a change—rather than restating the diff—is hard to do consistently, and opening PRs with the correct base branch, draft status, and linked issue requires careful use of the GitHub CLI. ## Core Features & Use Cases - Structured PR body: Generates a body with # Why (a single * Close #<issue> link), # How (the approach taken), and an optional # Note for caveats, with rules for when H2 subheadings are warranted. - Convention-driven titles: Titles open with the linked issue's type emoji and name the work at one altitude, never listing parts or repeating the branch name. - Safe gh CLI workflow: Reads open issues to match the one being closed, always opens PRs as drafts with --assignee @me, resolves the correct base branch by walking trunk markers, and hands over text alone when gh is unavailable. - Use Case: After finishing work on a feature branch, ask the agent to write and open the pull request; it identifies the linked issue, drafts the title and body for your review, then runs gh pr create --draft only after you approve. ## Quick Start Write a pull request for the current branch and open it as a draft against the correct trunk using gh.
