ship

Automates the release workflow of testing, reviewing, versioning, and creating pull requests for git branches.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill ship-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/adamtpang/summon.company --skill ship-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves many error-prone manual steps: merging the base branch, running tests, reviewing the diff, bumping versions, updating the changelog, and creating a PR. This Skill orchestrates that entire release pipeline so nothing gets skipped. ## Core Features & Use Cases - End-to-End Release Pipeline: Detects and merges the base branch, runs test suites, audits test coverage and plan completion, bumps VERSION, updates CHANGELOG, commits, pushes, and creates the PR/MR. - Multi-Layer Review: Runs pre-landing checklist reviews, specialist subagent reviews (security, performance, testing, maintainability), adversarial reviews from Claude and Codex, and Greptile comment triage before shipping. - Governance Gates: Blocks on critical findings, confirms unverifiable plan items individually, scans PR bodies for leaked credentials, and enforces version-prefixed PR titles. - Use Case: A developer finishes a feature branch and says "ship it" — the Skill runs tests, dispatches review specialists, generates the changelog from commit history, and opens a fully documented PR. ## Quick Start Ask the AI to ship the current branch by saying "ship it" or "create a PR" and it will run the full test, review, version, and pull request workflow.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ship a feature branch and create a PR automatically?

Invoke the ship workflow by saying "ship it" or "create a PR". It merges the base branch, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates the pull request with a generated body.

What review steps run before the pull request is created?

The workflow runs a pre-landing checklist review, specialist subagent reviews for security, performance, testing and maintainability, adversarial reviews from Claude and Codex, and Greptile comment triage. Critical findings can block the ship.

Does the ship workflow work with GitLab as well as GitHub?

Yes, it detects the platform and uses gh for GitHub pull requests or glab for GitLab merge requests. If neither CLI is available, it prints the branch and remote URL so you can create the PR manually.

What happens if Codex CLI is not installed during adversarial review?

The workflow detects Codex availability via a preflight check. If Codex is not installed or not authenticated, it falls back to the Claude adversarial subagent only and prints a note explaining how to enable cross-model coverage.

How is the CHANGELOG entry generated during shipping?

The workflow enumerates every commit on the branch, reads the full diff, groups commits by theme, and writes a categorized entry with Added, Changed, Fixed, and Removed sections. Every commit must map to at least one bullet point.

Can the ship workflow leak secrets into the PR body?

No. Before creating or editing a PR, the composed body and title are scanned with a redaction engine. High-severity credential findings block the PR entirely, and medium findings require explicit confirmation.