ship-it

Automate squash merging of verified Pull Requests with green CI status.

25|5|Updated May 9, 2026
One-click install
npx skills add https://github.com/kamp-us/phoenix --skill ship-it-kamp-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/kamp-us/phoenix/tree/main/claude-plugins/kampus-pipeline/skills/ship-it
Command: npx skills add https://github.com/kamp-us/phoenix --skill ship-it-kamp-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the merge of a Pull Request that has been verified as meeting all required criteria and has a green CI status.

Core Features & Use Cases

  • Merge Automation: Automates the squash merge of a verified Pull Request.
  • Verification: Ensures that the Pull Request has passed code, doc, or skill reviews and has a green CI status.
  • Use Case: Ideal for CI/CD pipelines to automatically merge Pull Requests that are ready for production, reducing manual merge work.

Quick Start

To ship a verified Pull Request, simply use the command "/ship-it #123".

Frequently Asked Questions about ship-it

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

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

Automated pull request merge tools trigger a squash merge once predefined criteria are met. They verify that the PR has passed all necessary code reviews and has a green CI status before executing the verified merge.

What is the best way to trigger a verified GitHub merge automatically?

The best way to trigger a verified GitHub merge automatically is by using a merge automation command like "/ship-it #123". This executes the merge once the PR is verified as meeting all required criteria.

Can I use merge automation to squash verified pull requests in my CI/CD pipeline?

Yes, you can use merge automation to squash verified pull requests in your CI/CD pipeline. It is ideal for development workflows to automatically merge pull requests that are ready for production and reduce manual merge work.

Does automated merge automation require passing code reviews and a green CI status?

Yes, automated merge automation requires passing code reviews and a green CI status. It ensures that the pull request has passed code, doc, or skill reviews before proceeding with the automated verified merge.

Why should I integrate pull request merge automation into my development workflow?

You should integrate pull request merge automation into your development workflow to reduce manual merge work. It automates the squash merge of verified pull requests that are ready for production, streamlining your CI/CD pipelines.