skills.rest
MartinoPolo
MartinoPoloCOMMUNITY
Explore all skills by this author →
GitHub

mp-ship

Synchronize base branch, push changes, and manage GitHub PRs with auto-merge.

1|Updated Feb 7, 2026
Search Tags:#pull request#git workflow#github#auto-merge#ci monitoring#tdd execution
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mp-ship
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/skills/mp-ship
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone process of finishing a GitHub PR by syncing the base branch, committing and pushing changes, merging the PR, and verifying that CI is green.

Core Features & Use Cases

  • End-to-end PR shipping flow: Detects repo state, syncs the base branch into the current branch, commits and pushes, opens the PR (or updates it), arms auto-merge, watches CI, and merges using the repo’s allowed merge strategy.
  • CI failure recovery loop: Diagnoses CI failures from GitHub Actions logs, applies code fixes, reruns failed jobs, and stops after a bounded number of attempts to avoid endless loops.
  • Post-merge housekeeping: Comments on the PR and synchronizes the main worktree by pulling the updated state back into the primary repo.

Quick Start

Use mp-ship with an optional base branch argument like "main" to merge your finished work and only proceed when CI is green.

Frequently Asked Questions about mp-ship

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

FAQPage Schema
How do I automate merging a GitHub pull request only after CI passes?▼

Automating a GitHub pull request merge after CI passes requires syncing the base branch, pushing commits, arming auto-merge, and watching CI checks until green. This workflow arms auto-merge with the repo's allowed merge strategy and monitors CI checks until successful.

What is the best way to handle GitHub Actions CI failures automatically after pushing a branch?▼

Handling GitHub Actions CI failures automatically involves diagnosing failures from Actions logs, applying code fixes, and rerunning failed jobs. This workflow uses a bounded failure recovery loop to diagnose logs, apply fixes, and rerun jobs to prevent endless cycles.

Do I need the GitHub CLI installed to automate my git workflow and PR creation?▼

Yes, you need the GitHub CLI installed to automate this git workflow and PR creation. The process must run gh-based GitHub operations to open or update pull requests, arm auto-merge, and monitor CI checks on your branch.

Can I sync my main worktree automatically after a pull request is merged?▼

Yes, you can sync your main worktree automatically after a pull request is merged. The workflow performs post-merge housekeeping by commenting on the PR and pulling the updated state back into the primary repo worktree.

How does a TDD execution workflow handle uncommitted changes when creating a PR?▼

A TDD execution workflow handling uncommitted changes when creating a PR detects the repository state first. This workflow detects whether a branch is uncommitted, committed-but-unpushed, or already pushed with an open PR, then syncs, commits, and pushes changes accordingly.

Related Skills

Explore More Software Engineering Skills→
shiimanshiiman
2

pr

Create or update GitHub Pull Requests from the current branch.

Community
Advanced
bbohhu-progbbohhu-prog

finishing-a-development-branch

Verify tests and present deterministic merge, PR, or cleanup options for Git feature branches.

Community
Advanced
GratefulJinx77GratefulJinx77

speckit-deploy

Automates post-merge deployment monitoring and Copilot review analysis.

Community
Advanced
HaveAPointHaveAPoint

auto-commit

Automate Git commits, pushes, and pull request creation.

Community
Intermediate