ship

Automate commit, push, and state transition for gated story shipping.

Updated Apr 7, 2026

Search Tags:#git #workflow #deployment #ship #pull-request #gate-review

Ready to run

npx skills add https://github.com/ramontramontini/CTEDemo --skill ship-ramontramontini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill ship-ramontramontini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship a story by performing the final commit, push, and state transition within a gated workflow. It ensures all quality work (tests, docs, compliance, drift, ship-review) is completed in /pull Step 4 before invoking /ship.

Core Features & Use Cases

End-to-end shipping workflow: commit, push, and transition to done after all gates pass.
Pre-flight validation and readiness checks to ensure required stamps and fields exist.
Gate-review integration and task reconciliation to align quality work with shipping.

Quick Start

Provide a STORYID to ship after verifying in_progress status and the review_ship stamp, then monitor the push and final transition steps.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate git commit, push, and state transition for a gated pull request workflow?▼

Automating git commit, push, and state transition requires a gated workflow that validates pre-flight checks and formal approvals before final execution. The process ensures all quality work like tests and compliance is completed, then performs the final push to transition the story to done.

What is a gated workflow for shipping software stories and bug fixes?▼

A gated workflow for shipping software stories is a formalized process enforcing quality checks and stamp validation before allowing a final code push. It ensures tasks like ship-review and compliance are verified, preventing incomplete work from transitioning to a done state.

Do I need a specific review stamp before shipping a story in a gated deployment?▼

Yes, shipping a story in a gated deployment requires a formal review_ship stamp and in_progress status verification. Pre-flight readiness checks validate the presence of these required stamps and fields before allowing the commit and push sequence to execute.

What is the best way to ensure quality checks are completed before pushing a git deployment?▼

The best way to ensure quality checks before pushing a deployment is using a structured pre-flight validation process. This approach reconciles tasks, validates required gate stamps, and confirms that all tests and documentation are finished prior to the final commit.

Why does my gated pull request fail readiness checks before final state transition?▼

Gated pull requests fail readiness checks when required pre-flight validations detect missing gate stamps, incomplete quality tasks, or invalid in_progress status. The workflow performs structured error handling to prevent pushing code that lacks the necessary formal approvals.

Can I use API interactions for task reconciliation during a git deployment workflow?▼

Yes, you can use API interactions via hub-client.sh for task reconciliation during a git deployment workflow. These API calls align quality work with shipping requirements, verify in_progress states, and facilitate the final gated transitions after passing readiness checks.