ship-guarded

Automates PR shipping with a pre-merge risk assessment gate for production-critical repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping changes to tools you rely on daily is risky: a broken merge can disrupt real workflows, but manually reviewing every PR for risk slows everything down. This Skill automates the full ship pipeline while pausing only when a change actually touches risk surfaces like user-facing flows, schemas, or auth code. ## Core Features & Use Cases - Full Ship Pipeline: Runs code review (Claude + codex in parallel), definition-of-done checks, PR creation, CI monitoring, and Copilot review monitoring. - Risk Surface Assessment: Evaluates the diff against five concrete risk surfaces (user-facing flows, removed features, schema/storage changes, perf-sensitive paths, external integrations) before merging. - Conditional Pause: Merges autonomously when no risk surface is touched; otherwise sends a single message with the implicated files, failure-mode assessment, suggested smoke test, and a merge/hold/split recommendation. - Use Case: You maintain a CLI tool you use every day. A dependency bump PR touches nothing risky, so it merges automatically; a PR modifying auth flow pauses with a targeted smoke-test suggestion before you approve the squash merge. ## Quick Start Use the ship-guarded skill to review, open, and merge the current branch's PR, pausing for my approval only if the diff touches user-facing flows, schemas, or other risk surfaces.

Frequently Asked Questions about ship-guarded

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

FAQPage Schema
How do I automatically merge GitHub PRs only when changes are low risk?▼

Run the ship pipeline, which evaluates the diff against five risk surfaces: user-facing flows, removed features, schema/storage changes, perf-sensitive paths, and external integrations. If none are touched, it merges with gh pr merge --squash --delete-branch; otherwise it pauses for your approval.

What is the difference between ship-guarded and ship-auto?▼

ship-guarded runs the same pipeline as ship-auto (code review, PR, CI, Copilot monitoring) but adds a structured risk assessment before merging. ship-auto merges autonomously; ship-guarded pauses when the diff touches defined risk surfaces.

Which code changes trigger a pause before merging?▼

Changes touching routes, page renders, form behavior, deleted endpoints or config keys, migrations, saved-data format changes, hot loops, request handlers, auth flows, payments, or third-party API contracts trigger a pause with a risk assessment and smoke-test suggestion.

Does ship-guarded still enforce D-class gates like breaking changes?▼

Yes. D-class gates remain in effect: breaking-change merges to the default branch, public deploys of breaking changes, external sends, irreversible deletes, and force-pushes always pause. The risk assessment is additional to D-class, not a replacement.

When should I not use a guarded ship pipeline?▼

Avoid it for repositories where breakage cost is low, such as experiments or throwaway prototypes, since the risk assessment step adds overhead. Use a fully autonomous ship pipeline like ship-auto for low-stakes repos instead.