ship

Automates the release workflow from branch merge through tests, review, version bump, and PR creation.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill ship-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/raghavbadhwar/rstack/tree/main/ship
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill ship-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves a long, error-prone checklist: merging the base branch, running tests, reviewing the diff, bumping the version, updating the CHANGELOG, committing, pushing, and opening 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, generates the CHANGELOG entry from commits, and creates or updates the PR/MR on GitHub or GitLab. - Multi-layer review gates: Runs a pre-landing checklist review, dispatches specialist reviewer subagents (security, performance, testing, maintainability, API contract, data migration, design), performs adversarial review with Claude and Codex, and triages Greptile PR comments. - Evidence-producing PR body: Composes a structured PR body with summary, test coverage, review findings, plan completion status, scope drift check, and documentation sync, with a redaction scan before publishing. - Use Case: After finishing a feature branch, tell the agent to ship it; the Skill re-runs tests, audits the diff against the original plan, fixes or surfaces review findings, bumps the version, writes the CHANGELOG, and opens a properly titled PR. ## Quick Start Ask the agent to ship the current branch and create a pull request for it.

Frequently Asked Questions about ship

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

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

Invoke the ship workflow on your feature branch. It merges the base branch, runs tests, reviews the diff with specialist and adversarial passes, bumps VERSION, updates the CHANGELOG, commits, pushes, and creates or updates the PR with a structured body.

What review checks run before the pull request is created?

The pipeline runs a pre-landing checklist review, dispatches specialist subagents for security, performance, testing, maintainability, API contract, data migration, and design based on diff scope, plus adversarial review from Claude and Codex when available.

Does the ship workflow support GitLab merge requests?

Yes. The workflow detects the hosting platform and uses glab to create or update merge requests on GitLab, or gh for pull requests on GitHub. If neither CLI is available, it prints the branch and remote URL for manual creation.

What happens if Codex CLI is not installed or authenticated?

The workflow checks Codex availability in a preflight step. If Codex is missing, unauthenticated, or disabled, it skips the Codex passes with a printed note and continues with the Claude adversarial subagent, which always runs.

How is the CHANGELOG entry generated during a release?

The workflow enumerates every commit on the branch, reads the full diff, groups commits by theme, and writes a categorized CHANGELOG entry with Added, Changed, Fixed, and Removed sections. It cross-checks that every commit maps to at least one bullet.

When is the Codex structured review skipped?

The Codex structured review only runs when the diff is 200 or more changed lines and Codex is ready. Smaller diffs rely on the Claude and Codex adversarial passes, and the review is skipped entirely if Codex is unavailable or disabled.