What problem does it solve? Turning a pile of uncommitted changes into a clean, reviewable pull request requires consistent branch naming, atomic commit splitting, and well-written PR descriptions—work that is repetitive and easy to get wrong. This Skill automates the entire flow from staging to opening the PR. ## Core Features & Use Cases - Conventional branch management: Creates or renames branches to the <type>/<short-description> convention (feat, fix, chore, etc.), including inside git worktrees. - Atomic commits: Splits changes by concern into separate commits with conventional commit subjects, imperative mood, and proper breaking-change footers, while never staging secret files. - PR creation via GitHub CLI: Pushes the branch and opens a PR with a ≤70-char title, inferred labels checked against gh label list, why-focused body bullets, and a mandatory test plan. - Use Case: After finishing a bug fix across several files, ask to open a PR—the Skill stages only relevant files, writes fix(auth): correct redirect loop style commits, pushes, and returns the PR URL. ## Quick Start Ask the assistant to create a pull request for your current changes, for example by saying "create a PR for these changes".