skills.rest
LaPaGaYo
LaPaGaYoCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automate release gating and merge readiness governance in Nexus.

1|Updated Mar 31, 2026
Search Tags:#workflow#merge#governance#ship#release-gate
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill ship-lapagayo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/ship
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill ship-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate and govern the release process to ensure only approved changes merge, reducing risk and rework.

Core Features & Use Cases

  • Gate pre-merge checks, track release readiness, and surface governance decisions.
  • Manage branch outcomes: merge, keep alive, discard, or split, with governance artifacts.
  • Provide a canonical path for /ship, integrate with nexus.skill.yaml and policy controls.

Quick Start

Run /ship when all pre-merge gates are green and blockers are resolved.

Frequently Asked Questions about ship

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

FAQPage Schema
What is release gating and how does it govern merge readiness?▼

Release gating automates governance by enforcing pre-merge criteria across lifecycle stages like /build, /review, and /qa to ensure only approved changes merge. It tracks readiness and generates artifacts like release-gate-record.md to surface governance decisions.

How do I automate branch outcomes for merge or discard decisions?▼

You can automate branch outcomes by running the canonical /ship flow, which evaluates gate criteria and determines whether to merge, keep alive, discard, or split branches. This ensures governed branch decisions based on release readiness.

When should I run the /ship flow in my development lifecycle?▼

You should run /ship when all pre-merge gates are green and blockers are resolved. It acts as the final release gate, applying policy controls and generating governance artifacts to verify merge readiness.

Can I use nexus.skill.yaml to configure policy controls for release gates?▼

Yes, the governance flow integrates with nexus.skill.yaml to apply policy controls across lifecycle stages. It reads the SKILL.md frontmatter and optional scripts to enforce gate criteria and manage branch outcomes.

What's the best way to track release readiness and governance decisions?▼

Track release readiness by using governance artifacts like release-gate-record.md, which surface decisions and gate criteria status. This provides a canonical record of pre-merge checks and branch outcomes throughout the process.

Related Skills

Explore More Software Engineering Skills→
supersterlingsupersterling
1

skill-creator

Create Claude skills with SKILL.md frontmatter and evaluation loops.

Community
Advanced
ilandahanilandahan
9

QA & Ship Phase Skill

Validates acceptance criteria and generates release notes and deployment artifacts.

Community
Advanced
euroconiceuroconic
1

feature-delivery

Automate feature delivery governance with enforced Git branch lifecycle rules and DELIVERY_TRACKER.md updates.

Community
Advanced
remiboivin021remiboivin021

release

Evaluate feature branches against acceptance criteria and output a MERGE READY or NOT READY verdict.

Community
Advanced