How do I install the Shipit skill?

Run npx skillmds@latest add bostonaholic/shipit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shipit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shipit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shipit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shipit?

bostonaholic (@bostonaholic) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shipit by bostonaholic — Agent Skill

Name: Shipit
Author: bostonaholic

File contents

shipit — land a reviewed PR

shipit lands a pull request that already passed review. It pushes any unpushed local commits, waits for CI to go green, and squash-merges. The PR title then lands as the commit subject on the base branch. If a project puts a version in the title, that version shows up in git log. It finalizes an existing open PR, and never opens one. It is generic, and it does no versioning, changelog editing, or release work. If a project assigns a version at land time, that happens in a separate project-specific step before /shipit (in this repo, the dev version-bump skill — see docs/versioning.md). shipit only cares that the branch is ready to land.

gh pr merge is irreversible, so two things guard it — neither of them a frontmatter flag, and neither of them a question put to the user mid-run:

Explicit ship intent. The skill fires only on a direct "ship it" / "land the PR" / /shipit. An approved, green, or finished-looking PR is not ship intent — the user decides when to land.
CI green (step 3), which gates the merge mechanically — a red or timed out check stops the land before gh pr merge ever runs.

The first guard is principle-explicit-intent applied to the merge: an irreversible act fires on stated intent, never on state, and granted authorization is spent, not re-asked.

Do not ask the user to confirm the merge. Ship intent already carried the authorization to merge, so a confirmation re-requests permission the invocation granted, and every caller that chains into /shipit inherits the stop. Once step 3 reports green, merge. The guard against merging the wrong thing is refusing to start without ship intent, not stopping halfway through a land the user asked for.

Ticket completion comes from the PR body's Closes #<n> link; this skill performs no board mutation.

Procedure references

Read each reference completely when reaching that stage. Follow them in order; later stages depend on state and gates established earlier.

Input acquisition
Land sequence

Applied principles

Load and apply: principle-non-blocking-waits.

---name: shipitdescription: Lands a reviewed pull request. Trigger on "ship it", "land the PR", "land this", or "/shipit" only; never infer ship intent from approval, green CI, or completion.---# shipit — land a reviewed PR`shipit` lands a pull request that already passed review. It pushes any unpushedlocal commits, waits for CI to go green, and squash-merges. The PR title thenlands as the commit subject on the base branch. If a project puts a version inthe title, that version shows up in `git log`. It**finalizes an existing open PR**, and never opens one. It is generic, and itdoes no versioning, changelog editing, or release work. If a project assigns aversion at land time, that happens in a separate project-specific step *before*`/shipit` (in this repo, the dev `version-bump` skill — see[docs/versioning.md](../../docs/versioning.md)). `shipit` only cares that thebranch is ready to land.`gh pr merge` is irreversible, so two things guard it — neither of them afrontmatter flag, and neither of them a question put to the user mid-run:1. **Explicit ship intent.** The skill fires only on a direct "ship it" / "land the PR" / `/shipit`. An approved, green, or finished-looking PR is *not* ship intent — the user decides when to land.2. **CI green** (step 3), which gates the merge mechanically — a red or timed out check stops the land before `gh pr merge` ever runs.The first guard is `principle-explicit-intent` applied tothe merge: an irreversible act fires on stated intent, never on state, andgranted authorization is spent, not re-asked.**Do not ask the user to confirm the merge.** Ship intent already carried theauthorization to merge, so a confirmation re-requests permission the invocationgranted, and every caller that chains into `/shipit` inherits the stop. Oncestep 3 reports green, merge. The guard against merging the wrong thing isrefusing to start without ship intent, not stopping halfway through a land theuser asked for.Ticket completion comes from the PR body's `Closes #<n>` link; this skill performs no board mutation.## Procedure referencesRead each reference completely when reaching that stage. Follow them in order; later stages depend on state and gates established earlier.1. [Input acquisition](references/01-input-acquisition.md)2. [Land sequence](references/02-land-sequence.md)## Applied principlesLoad and apply: `principle-non-blocking-waits`.

Frequently asked questions

Shipit