ship

Automate PR finalization and squash merges after CI and review validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/o3-ozono/atdd-kit --skill ship-o3-ozono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/o3-ozono/atdd-kit/tree/main/skills/ship
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill ship-o3-ozono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures end-to-end PR finalization and merge readiness after verification passes, enforcing guardrails so only fully reviewed and approved changes reach main.

Core Features & Use Cases

  • Enforces a complete PR lifecycle: gating, labeling, and review checks before merge.
  • Automates squashed merges on CI-green PRs to maintain a clean git history.
  • Use Case: When a feature has passed all verifications and QA, ship finalizes the PR and moves it toward release with required approvals.

Quick Start

Run the ship skill after verify passes to push the PR through the final review and merge workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate GitHub PR merges after CI verification passes?

Automating GitHub PR merges after verification passes requires enforcing state gates, checking the main branch, and validating CI review statuses before performing a squash merge to finalize the release. This ensures compliant changes reach main.

What is the best way to enforce PR review checks before a squash merge?

To enforce PR review checks before a squash merge, apply gating, labeling, and review validation across the GitHub PR lifecycle to ensure only fully approved and CI-green changes are merged, maintaining a clean git history.

How does a draft PR transition to ready-for-review before finalizing?

A draft PR transitions to ready-for-review through state gating that enforces readiness checks before finalization, ensuring the PR meets all required approval and verification conditions before moving toward a merge.

Can I use automated squash merging to maintain a clean git history on main?

Yes, automated squash merging on CI-green PRs maintains a clean git history by enforcing end-to-end PR finalization guardrails, ensuring only fully reviewed and approved changes are squashed and merged into the main branch.

Why does my PR finalization workflow fail when gating and review checks are incomplete?

PR finalization workflows fail when gating and review checks are incomplete because the merge process enforces strict guardrails, requiring CI validation, proper labeling, and ready-for-review states to be fully satisfied before merging.