ship-it

Merge reviewed GitHub pull requests and update issue statuses.

3|Updated Aug 28, 2025
One-click install
npx skills add https://github.com/mrgeoffrich/mini-infra --skill ship-it-mrgeoffrich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/mrgeoffrich/mini-infra/tree/main/.claude/skills/ship-it
Command: npx skills add https://github.com/mrgeoffrich/mini-infra --skill ship-it-mrgeoffrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the process of squashing, merging, and transitioning issue statuses after review, reducing manual effort and preventing inconsistencies.

Core Features & Use Cases

  • Automated PR Merge: Performs a squash merge on GitHub for specified issues, ensuring a clean commit history.
  • Issue State Transition: Updates the related issue in mk from in_review to done, keeping project boards accurate.
  • Use Case: When a team member completes a code review and approves a PR, this Skill automatically merges the PR and marks the issue as complete, streamlining release workflows.

Quick Start

To merge a review-ready PR for issue MINI-42, tell the AI "ship MINI-42" and it will handle the process from validation to closing.

Frequently Asked Questions about ship-it

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

FAQPage Schema
How do I automate merging reviewed pull requests on GitHub?

You can automate merging reviewed pull requests on GitHub by using an automation Skill to validate review and build statuses, perform a squash merge, and transition linked issue states automatically.

What is the best way to keep project management issue statuses accurate after a PR merge?

The best way to keep project management issue statuses accurate after a PR merge is to automate the state transition, moving linked issues from in_review to done immediately upon successful merge completion.

How do I squash and merge a pull request without manual checks?

You can squash and merge a pull request without manual checks by triggering an automated workflow that verifies review approval and build status before executing the GitHub squash merge operation.

Can I automatically transition issue states when a GitHub PR is merged?

Yes, you can automatically transition issue states when a GitHub PR is merged by configuring an automation workflow that updates the project management tool to mark the issue as done.

Does automated PR merging check build status before completing the squash merge?

Yes, automated PR merging checks both review approval and build status before completing the squash merge to ensure only validated, passing code is integrated into the main branch.

What are the limitations of automating GitHub merges and issue transitions?

Automating GitHub merges and issue transitions relies on specific issue tracking tools like mk and requires successful build and review validation, meaning it cannot bypass failed checks or force incomplete merges.