# Ship Pr

> Use when the user wants a change shipped autonomously end to end: commit, push, open the PR, watch CI, triage and address bot/human review comments in-thread, resolve threads, and merge when everything is green ('ship it', 'run the full PR cycle', 'commit, push, PR, and merge if clean'). Runs to merge without per-step asks. NOT for stepwise asks: pushing only, opening a PR only, addressing review feedback only, or merging an existing PR only (push-pr owns those).

- Skill: `ryan-brosas/ship-pr` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ryan-brosas/ship-pr`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ryan-brosas/ship-pr/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ryan-brosas (https://skillmd.com/u/ryan-brosas)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ryan-brosas/ship-pr

---


# Ship PR

This is the orchestration layer for an explicitly requested full lifecycle through
merge. Individual push, PR, review, or merge requests belong to
`../push-pr/SKILL.md`. Full-cycle authorization permits merge, but evidence still
gates it. If the repository has no quality gate, report that gap instead of
inventing CI or claiming a clean full cycle.

## Loop

1. Inspect authored scope and the requested/default base. Create a branch and
   scoped conventional commits without unrelated changes. Run the repository's
   gates on the committed tree and `git diff --check <base>..HEAD`. A red local
   gate blocks push.
2. Load `../push-pr/SKILL.md` and use its evidence, template, PR creation/update,
   and metadata procedure. Do not duplicate endpoint mechanics here.
3. Watch required CI to a final state. Read review findings, not just review-bot
   status. For each feedback cycle, use
   `../push-pr/references/review-threads.md`: verify findings against source, fix
   and test valid issues, commit/push, reply in-thread, then resolve appropriately.
   Rebut invalid findings with evidence in-thread; leave them open for reviewer
   confirmation when needed. A reply alone never resolves a thread.
4. For conflicts, integrate the current base and rerun gates before pushing.
   Repeat verification after every fix; stop and report findings requiring a
   human decision.
5. Merge only with `mergeStateStatus: CLEAN`, green local gates and required CI,
   and every review thread resolved. Use a repository-allowed merge method;
   never bypass protections. Auto-merge is not implied by repository capability.
6. Delete the merged task branch and sync the local base without discarding user
   work. If local changes prevent safe cleanup, report the remaining cleanup
   rather than reset them.

Verify completion with `gh pr view <n> --json state,mergedAt,mergeCommit,statusCheckRollup`
(`MERGED`, a merge SHA, and every rollup check passing) plus paginated GraphQL
`reviewThreads.isResolved` all true. Report the PR link, merge SHA, and any
cleanup limitation. Commit/merge conventions belong to
`../git-workflow-and-versioning/SKILL.md`.