ship

Automate CI/CD merge and deployment for GitHub pull requests.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/qvidal01/claude-code-skills --skill ship-qvidal01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/qvidal01/claude-code-skills/tree/main/ship
Command: npx skills add https://github.com/qvidal01/claude-code-skills --skill ship-qvidal01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of pushing code, ensuring a pull request exists, watching CI, and merging code when all checks are green, reducing manual intervention in the CI/CD pipeline.

Core Features & Use Cases

  • Automated Merge: Pushes code, creates a pull request if necessary, watches CI, and merges code when all checks pass.
  • Conditional Merge: Allows for conditional merging based on specific PR numbers or branch names.
  • Merge Verification: Provides verification of review-bot verdicts before merging, ensuring code quality and compliance.
  • Use Case: For developers looking to streamline the deployment process, this Skill can be used to automatically merge code into a main branch once all checks have passed, reducing the time spent on manual merges.

Quick Start

Run the 'ship' command to automatically merge the current branch once all required checks are green.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a GitHub pull request merge when CI checks pass?

To automate a GitHub pull request merge when CI checks pass, you can use a merge automation tool that watches required checks and triggers the merge automatically once they are green. This eliminates manual intervention in the deployment pipeline.

Can I conditionally merge a specific pull request or branch based on CI status?

Yes, you can conditionally merge a specific pull request or branch based on CI status by configuring merge automation rules. These rules verify that all required CI checks are green before triggering the merge for the specified PR number or branch name.

Do I need the gh CLI installed to automate GitHub deployments?

Yes, you need the gh CLI installed to automate GitHub deployments with this approach. The merge automation process requires the gh CLI for GitHub integration to push code, monitor CI, and trigger merges.

How does review-bot verification work before merging code?

Review-bot verification before merging code works by checking the review-bot verdicts to ensure code quality and compliance. The merge automation process queries these verdicts and only proceeds with the merge if the review-bot verification passes.

What is the best way to streamline a CI/CD pipeline and reduce manual merges?

The best way to streamline a CI/CD pipeline and reduce manual merges is to implement automated merge verification. This approach pushes code, creates a pull request if necessary, watches CI, and merges automatically when all required checks pass.