What problem does it solve? Creating pull requests often leads to inconsistent commit messages, unscoped staging, missing context for reviewers, and forgotten team notifications. This Skill enforces a repeatable PR workflow so every pull request follows the same conventions for staging, committing, pushing, description formatting, and team communication. ## Core Features & Use Cases - Scoped Staging and Conventional Commits: Stages only changes belonging to the PR and commits with type(scope): description messages using types like feat, fix, refactor, docs, test, and chore. - Structured Draft PR Creation: Uses gh pr create to open draft PRs with a title matching the commit message and a body organized into Why, Changes, and Test plan sections, with no tool attribution. - Slack Follow-Up Message: Generates a casual Slack ping summarizing the PR so teammates are notified immediately after creation. - Use Case: After finishing a bug fix on a feature branch, invoke the Skill to stage only the relevant files, commit with a conventional message, push the branch, open a draft PR with a reviewer-friendly body, and get a ready-to-send Slack message. ## Quick Start Create a pull request for my current branch following the standard conventions and draft the Slack message for my teammate.