git-pr
Skill: git-pr
Purpose
The default agent behavior is to treat "ship it" as one undifferentiated act — git add -A && git commit -m "fix" && git push — and to treat reviewer comments and red CI as someone else's problem.
Each shortcut fails silently in a way nobody notices until later: add -A sweeps a secret or an
unrelated edit into history; a one-word commit message erases the why the next reader needs; a PR
with no verification steps makes the reviewer reconstruct your intent from the diff; a blind CI
re-run burns minutes and hides a real bug; parallel branches in one checkout overwrite each other's
work. This guide makes shipping a disciplined sequence — stage, commit, push, then open a PR when
the repository uses one, and close the loop on review and CI — so the change lands the way you meant
it to.
The ship loop here is stage → commit → push, plus a PR when required, review-comment closure, and CI follow-through. Parallel work uses git worktrees.