What problem does it solve? Moving code from local changes to a reviewed pull request involves many error-prone steps: naming branches to match tickets, running lint and type checks, writing clean commits, and drafting reviewer-friendly PR bodies. This Skill standardizes that entire pipeline so nothing gets skipped. ## Core Features & Use Cases - Branch and Commit Discipline: Enforces ticket-keyed branch names, staged-file scoping, and imperative commit messages without AI attribution trailers. - Pre-commit Quality Gates: Runs lint, formatters, type checks, and tests on changed files before any commit is allowed. - Structured PR Creation: Uses the gh CLI to create PRs with a four-section body contract (Description, Verification, Test Instructions, Note), assigns reviewers, and requests Copilot review. - Use Case: After finishing a bug fix on branch DSC-1986-fix-rails-sticky, ask the agent to run the full workflow — it lints and tests the changed files, commits only relevant changes, and opens a PR with before/after reproduction evidence and a Jira link. ## Quick Start Create a branch for ticket DSC-1986, commit my staged changes after running lint and type checks, and open a pull request with test instructions.
