ship

Commit feature branch work, open a pull request, and merge to main.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill ship-kapilvirenahuja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/ship
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill ship-kapilvirenahuja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of manually committing changes, opening a PR, running an optional quality gate, merging to main, and cleaning up the feature branch by automating the end-to-end delivery pipeline.

Core Features & Use Cases

  • End-to-end branch delivery: Commits all uncommitted work on the current feature branch, creates and submits a PR, and merges it into main.
  • Optional quality gate enforcement: Runs the review-pr gate only when review-pr.bypass is false, halting on block/escalate.
  • Evidence + learning capture: Records PR/merge outcomes and triggers distill in the background, then captures distill results in ship evidence.
  • Automatic cleanup & validation: Switches to main, pulls latest, deletes the feature branch, and verifies scenario acceptance criteria.

Quick Start

Run the ship play while you are on your feature branch to automatically commit, open a PR, optionally enforce review-pr, merge into main, update your checkout, and delete the feature branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a git workflow to merge a feature branch into main?

Automating a git workflow to merge a feature branch into main requires committing uncommitted work, creating a pull request, optionally running a quality gate, and merging with branch cleanup. This Skill handles that end-to-end delivery pipeline in one shot.

What is a quality gate in a pull request delivery pipeline?

A quality gate in a pull request delivery pipeline is an optional review-pr enforcement step that halts the merge process on block or escalate outcomes when review-pr.bypass is false, ensuring code meets standards before promotion to main.

Can I bypass the review-pr quality gate when promoting a branch to main?

Yes, you can bypass the review-pr quality gate by setting the review-pr.bypass configuration to true, which skips the conditional review-pr routing and allows the feature branch to merge directly into main without halting.

What's the best way to capture evidence and validate a branch after merging to main?

The best way to capture evidence and validate a branch after merging to main is to trigger a non-blocking distill process in the background, record PR and merge outcomes, and verify scenario acceptance criteria against post-merge validation mappings.

How does branch cleanup work after merging a pull request into main?

Branch cleanup after merging a pull request into main involves switching to the main branch, pulling the latest changes, and automatically deleting the local feature branch to ensure a deterministic and repeatable promotion process.

What happens if pre-flight validation fails when delivering a feature branch?

If pre-flight validation fails when delivering a feature branch, the delivery pipeline halts because the process requires mandatory SKILL entry and pre-flight config validation, providing scenario and evidence reporting with recovery mappings to diagnose the issue.