skills.rest
rshelekhov
rshelekhovCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automate end-to-end PR shipping with base-branch merge, tests, and diff review.

Updated Nov 11, 2025
Search Tags:#automation#git#versioning#pr#ci-cd#ship#tests
One-click install
npx skills add https://github.com/rshelekhov/dotfiles --skill ship-rshelekhov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/rshelekhov/dotfiles/tree/main/claude/skills/gstack/ship
Command: npx skills add https://github.com/rshelekhov/dotfiles --skill ship-rshelekhov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end PR shipping by coordinating a base-branch merge, test execution, and diff review.

Core Features & Use Cases

  • Pre-flight merge and test orchestration against the base branch for a feature branch
  • Automatic version bump and CHANGELOG update as part of PR creation
  • One-click, non-interactive PR shipping for reliable release cycles

Quick Start

Run /ship to execute the full ship workflow on your current 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 PR shipping from a feature branch?▼

Automate PR shipping by running a single command to merge the base branch, execute tests, review diffs, bump versions, update the CHANGELOG, push commits, and open a pull request automatically.

Can I automatically update the CHANGELOG and bump versions when creating a PR?▼

Yes, automatic version bumps and CHANGELOG updates are integrated directly into the PR creation workflow, ensuring your project versioning stays current without manual intervention.

How does a non-interactive release workflow handle base branch merges?▼

Non-interactive release workflows handle base branch merges by automatically pre-flight merging the base branch into your feature branch and running tests to ensure deterministic, ship-ready PR workflows.

Do I need to manually run tests before creating a pull request?▼

No, test execution is orchestrated automatically against the base branch as part of the PR shipping workflow, ensuring your feature branch is fully validated before the pull request is created.

What is the best way to ensure deterministic PR creation in software projects?▼

The best way to ensure deterministic PR creation is to use an automated, non-interactive workflow that coordinates merges, tests, diff reviews, and version updates with minimal manual intervention.

Related Skills

Explore More Software Engineering Skills→
ReinaMacCredyReinaMacCredy
223

finishing-a-development-branch

Verify tests and present merge, PR, or cleanup options for a development branch.

Community
Advanced
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced
aimasteraccaimasteracc
46

ship

Automate the end-to-end ship workflow for code changes.

Community
Advanced
KakarottooooKakarottoooo

ship

Merge base branch, run tests, bump VERSION, update CHANGELOG, and create a pull request.

Community
Advanced