ship-push-only

Implements, tests, reviews, and pushes feature branches without opening pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In advisory or team-owned repositories, humans own the PR review, merge, and deploy process. This Skill ensures Claude completes implementation, testing, and code review, then pushes a clean feature branch and stops—never opening PRs, merging, or deploying on the team's behalf. ## Core Features & Use Cases - Bounded Shipping Pipeline: Runs parallel code review (Claude review plus codex review), fixes blocking findings, verifies the definition of done, and pushes the feature branch. - Strict Handoff Boundaries: Explicitly forbids gh pr create, merging, deploying, or messaging the team directly; all downstream actions stay with the human reviewer. - Reviewer-Ready Notification: Surfaces branch name, commit summary, diff stats, test status, non-blocking review findings, and a suggested PR title and description for the human to paste. - Use Case: You are contributing to a client repository with many production users and a team-owned review process. Use this Skill to deliver a tested, reviewed branch and hand off cleanly without touching the team's PR workflow. ## Quick Start Use the ship-push-only skill to finish this feature, run the code review, push the branch, and hand off a summary for the reviewer without opening a PR.

Frequently Asked Questions about ship-push-only

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

FAQPage Schema
What are the limitations of the push-only handoff approach?▼

Claude cannot merge, deploy, or address review feedback that has not been written yet, so progress pauses until the human reviewer acts. If the team later automates its flow, the project should switch to ship-auto or ship-guarded instead.