ship

Automate Git shipping with verification gates, conventional commits, and PR creation.

41|7|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/DGouron/review-flow --skill ship-dgouron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/DGouron/review-flow --skill ship-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping code changes from development to review stages is error-prone and tedious. This skill automates the end-to-end process by chaining verification, staged commit, push, and optional PR creation and merge, ensuring guardrails are respected and workflows stay consistent.

Core Features & Use Cases

  • Enforces quality gates before shipping: verification, linting, tests, and branch protections.
  • Automates commit composition using Conventional Commits and scoped messages.
  • Orchestrates push to origin and optional PR creation and merge, minimizing manual steps for developers on GitHub/GitLab workflows.
  • Use Case: A developer finishes a feature, runs the ship command, and the system validates, commits, pushes, opens a PR, and merges when approved.

Quick Start

Instruct the AI to execute the full ship workflow on the current feature branch: verify, stage, commit with a conventional message, push to origin, and optionally create and merge a PR.

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 pull request creation in one step?

You can automate git commit, push, and PR creation by chaining verification gates, conventional commits, and optional PR merge into a single workflow. This enforces branch protections and minimizes manual steps for GitHub or GitLab development.

What are conventional commits and how do they work with automated pull requests?

Conventional commits are a standardized messaging format used to automate commit composition. When paired with automated pull requests, the system stages changes and generates scoped conventional commit messages before pushing to origin and optionally creating a PR.

Can I enforce linting and tests before pushing code to GitHub or GitLab?

Yes, you can enforce linting and tests before pushing code by applying quality verification gates. The workflow runs pre-push checks, validates staged commits, and respects branch protection rules on GitHub or GitLab before proceeding with push or PR operations.

What is the best way to handle branch protection and PR merges automatically?

The best way to handle branch protection and PR merges automatically is to orchestrate push to origin and optional PR creation with safety checks. This applies guardrails throughout the end-to-end code shipping process, merging only when approved.

Does automated code shipping work with both GitHub and GitLab workflows?

Automated code shipping works with both GitHub and GitLab workflows. It applies to Git workflows where teams require guardrails, branch protection, pre-push checks, and automated collaboration for staged commits, PR creation, and optional merge operations.

Why do I need verification gates before staging commits and creating pull requests?

Verification gates are needed before staging commits to prevent error-prone code from reaching review stages. They enforce quality checks like linting and testing, ensuring branch protections are satisfied before pushing to origin and opening a pull request.