ship

Automate the end-to-end software release process with tests, version updates, and pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, codex, CLAUDE.md, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the entire software release process, from running tests to updating the CHANGELOG, committing changes, and creating a pull request.

Core Features & Use Cases

  • Automated Release Workflow: Detects the base branch, runs tests, reviews diffs, updates version, CHANGELOG, commits changes, pushes to main, and creates a pull request.
  • Customizable Tools: Allows the use of various tools like Bash, Read, Write, Edit, Grep, Glob, Agent, AskUserQuestion, and WebSearch.
  • Triggers: Can be invoked using specific triggers like "ship it", "create a pr", "push to main", "deploy this", or by proactively invoking the skill when the user indicates the code is ready.
  • Plan Mode: Operates safely within plan mode, ensuring the release process adheres to the defined plan.
  • Adversarial Review: Conducts adversarial reviews from both Claude and Codex to identify potential issues before release.

Quick Start

To ship your code, simply invoke the 'ship it' command when you believe the code is ready for release.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the software release process from running tests to creating a pull request?

To automate the software release process, you can use a single command to detect the base branch, run tests, review diffs, update the version and CHANGELOG, commit changes, push to main, and create a pull request.

What is an adversarial review in the context of continuous integration and deployment?

An adversarial review in continuous integration is a thorough code quality check where both Claude and Codex independently analyze diffs to identify potential issues before pushing changes to main.

Can I use git and Codex together for release automation within plan mode?

Yes, release automation can operate safely within plan mode using git and Codex, ensuring the software deployment process adheres to the defined plan while conducting adversarial reviews for code safety.

What's the best way to ensure version control safety before pushing to main?

The best way to ensure version control safety before pushing to main is to conduct adversarial reviews from both Claude and Codex, run tests, and review diffs automatically before committing changes.

Does the automated release workflow require a CLAUDE.md file to update the CHANGELOG?

Yes, the automated release workflow requires a CLAUDE.md file along with git and Codex as dependencies to detect the base branch, update versions, and properly manage the CHANGELOG during deployment.

Why should I use automated triggers like 'ship it' instead of manual software deployment?

Using automated triggers like 'ship it' for software deployment ensures completeness and safety by handling the entire release workflow end-to-end, reducing the risk of human error during version control and pull request creation.