ship-auto

Automates the full code review, PR, CI, merge, and deploy pipeline without human checkpoints.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill ship-auto-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-auto
Source: https://github.com/fryanpan/ai-team-lead/tree/main/plugin/team-lead-fleet/skills/ship-auto
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill ship-auto-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code normally involves repeated manual checkpoints — asking to commit, open a PR, wait on CI, address review comments, merge, and deploy. This Skill removes that friction by running the entire pipeline autonomously, pausing only for genuinely risky D-class changes like breaking changes, external sends, or irreversible deletes. ## Core Features & Use Cases - Parallel multi-agent code review: Dispatches Claude, Codex, and adversarial reviewers simultaneously, merging BLOCKING and ADVISORY findings before proceeding. - Channel-driven CI and Copilot monitoring: Reacts to GitHub events instead of polling, with fix-forward retries (up to 3 attempts) before escalating. - Automatic merge and deploy: Squash-merges the PR and triggers the project's deploy command without asking for confirmation. - Use Case: After implementing a feature on a branch in a personal repo, invoke this Skill to get the change reviewed, tested, merged, and deployed while you focus on other work. ## Quick Start Ship the current branch end to end — review it, open a PR, wait for CI and Copilot review, then merge and deploy without stopping to ask me.

Frequently Asked Questions about ship-auto

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

FAQPage Schema
How do I automatically merge a GitHub PR after CI passes?▼

Use gh pr merge with the --squash --delete-branch flags after CI checks pass. This Skill monitors CI via GitHub channel events rather than polling, then merges automatically once checks and Copilot review succeed.

How to run parallel AI code reviews on a git diff?▼

Dispatch multiple background review agents simultaneously against git diff of the base branch, giving each a return contract of file:line findings only. This Skill runs Claude, Codex, and adversarial reviewers in parallel and merges their BLOCKING and ADVISORY findings.

When does the auto-ship pipeline stop and ask for approval?▼

It pauses only for D-class events: breaking changes merged to the default branch, public deploys of breaking changes, external sends like emails or comments, irreversible deletes, and force-pushes to shared branches. Everything else proceeds without confirmation.

What happens when CI fails during an automated ship?▼

The pipeline reads the failure with a single gh pr checks call, fixes the issue, pushes, and awaits the next CI event. After three failed fix attempts it escalates to the user and stops.

Does this workflow require GitHub Copilot review to be configured?▼

No. If no Copilot review event arrives within five minutes, the pipeline assumes Copilot is not configured and proceeds to merge. When configured, it addresses requested changes with one retry before continuing.