ship

Automate a gated pre-merge pipeline that validates code and creates a pull request.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill ship-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/ship
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill ship-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents risky releases by enforcing a consistent pre-merge pipeline that validates, summarizes, and opens a pull request only when quality checks and tests pass.

Core Features & Use Cases

  • Pre-flight safety checks: Blocks shipping from main/master, verifies git readiness, ensures there are commits ahead of the base branch.
  • Test gate with smart SKIP behavior: Runs common test runners automatically (Makefile, npm, pytest, Go, bats) and blocks on test failures while marking “no tests found” as SKIP.
  • Quality gate for diff hygiene: Scans the proposed changes for likely secrets plus warnings for TODO/FIXME/debug artifacts, requiring user confirmation for warnings.
  • Diff summary and scope discipline: Produces a clear summary of commits/files/line changes to support reviewer confidence.
  • Versioning and changelog updates (optional): Detects VERSION/package.json and CHANGELOG.md, then prompts to bump version and updates changelog based on conventional commits.
  • Delegated commit + PR creation: Hands off to commit-commands:commit-push-pr to stage only specific files, avoid git add -A, and follow PR formatting conventions.

Quick Start

Tell the AI to run ship by invoking the command to execute the pre-merge pipeline and open a PR when all required gates pass.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a pre-merge pipeline with test gates and pull request creation?

You can automate a pre-merge pipeline by running tests, scanning diffs for quality issues, and delegating commit and PR creation. This process blocks failing tests and missing runners, ensuring code changes are validated before merging.

How does a test quality gate handle missing test runners in a CI automation pipeline?

A test quality gate automatically detects common test runners like Makefile, npm, pytest, Go, and bats. If no tests are found for a runner, the pipeline marks it as SKIP rather than failing, while still blocking the pipeline on actual test failures.

How do I prevent secrets and debug artifacts from being merged in a pull request?

To prevent risky merges, a quality gate scans proposed git diffs for likely secrets and debug artifacts like TODO or FIXME. It then requires explicit user confirmation for these warnings before allowing the pull request creation to proceed.

Can I automatically bump versions and update changelogs during a pre-merge workflow?

Yes, the pre-merge workflow optionally detects VERSION, package.json, and CHANGELOG.md files. It prompts you to bump the version and automatically updates the changelog based on conventional commits before opening the pull request.

Does the pre-merge pipeline block commits directly to the main or master branch?

Yes, the pre-merge pipeline enforces pre-flight safety checks that block shipping directly from main or master branches. It verifies git readiness and ensures you have commits ahead of the base branch before proceeding.

How does the pipeline stage and commit specific files without using git add -A?

The pipeline delegates staging and commit operations to avoid using git add -A, ensuring only specific files are staged. It hands off to commit-push-pr conventions to format and create the pull request safely.