Orchestrates a staged pipeline from working tree changes to a green, mergeable GitHub pull request.
npx skills add https://github.com/nsollazzo/ship-kit --skill ship-nsollazzo
Please help me install this Agent Skill. Skill: ship Source: https://github.com/nsollazzo/ship-kit/tree/main/.agents/skills/ship Command: npx skills add https://github.com/nsollazzo/ship-kit --skill ship-nsollazzo
--fast, --merge, --no-verify, and --yolo flags to control depth and hands-off behavior; failed stages halt loudly instead of being skipped silently. - End-to-end PR lifecycle: Drives the PR to fresh APPROVED + CI green + mergeable via the babysit stage, and optionally squash-merges and monitors the triggered deployment with --merge. - Use Case: You finished a bug fix on a feature branch. Invoke the ship pipeline to clean up the diff, run tests, apply review fixes, commit with conventional messages, open the PR, and let it babysit the PR until it is green and mergeable. ## Quick Start Ask the agent to ship the current change, for example: "Ship this change" or "Ship it with --merge to squash-merge and monitor the deployment once it goes green."High-intent search queries and answers about installing and using this skill.
Invoke the ship pipeline, which runs simplify, verify, code-review, and smart-commit stages, then pushes the branch and opens a PR with gh pr create. It pauses at one checkpoint for your confirmation before pushing unless you pass --merge or --yolo.
The ship pipeline's Stage 8 invokes the bundled babysit skill, which loops on the PR: verifying each review finding against the code, fixing valid ones, replying on threads, and pushing until the PR is freshly approved, all CI checks pass, and it is mergeable.
No, by default it stops at approved, CI green, and mergeable, leaving the merge to a human. Passing --merge authorizes a squash-merge followed by deployment monitoring via the merge-and-monitor skill.
Yes, --fast skips the simplify and code-review stages, and --no-verify skips the runtime verification stage, though the rebase-against-base check still runs. Skipped stages are always named explicitly in the final summary.
A failed stage halts the pipeline with the failure evidence rather than continuing. The skill writes a .ship-state.json file after each stage, so a later invocation on the same branch can offer to resume from the next unfinished stage.
Soyio-idCreate logically scoped git commits with Conventional Commit messages from working-tree changes.
adryanmoldokkr32-pixelMerge pull requests, monitor CI, deploy to production, and verify health with canary checks.
patrobRun parallel hypotheses to isolate root causes and require failing tests before patching.
richardwuFixes GitHub pull request review comments and CI check failures locally, commits and pushes updates.