ship

Merge feature branches, run tests, bump version, update changelog, and create pull requests.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/fghaffar/faystack --skill ship-fghaffar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/fghaffar/faystack/tree/main/ship
Command: npx skills add https://github.com/fghaffar/faystack --skill ship-fghaffar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes the manual, error-prone steps required to land a feature branch: syncing with the base branch, running tests, resolving simple conflicts, bumping version, updating the changelog, committing, pushing, and opening a pull request, while producing an auditable outcome and PR URL.

Core Features & Use Cases

  • End-to-end automation: Fetch and merge the base branch, run the test suite, and proceed only when automated checks pass or handle triage when they fail.
  • Release hygiene: Automatically bump VERSION (micro/patch by default), update CHANGELOG from commit diffs, and split multi-file changes into bisectable commits.
  • PR creation and evidence: Commit, push, and create a pull request with changelog and review readiness info, plus telemetry and a final PR URL.
  • Gating and safety: Stops for complex merge conflicts, major version bumps, failing critical checks, or review items that require human judgment.
  • Use case: A developer with a feature branch ready to land wants a single non-interactive workflow to produce a test-verified PR for review and merge.

Quick Start

Run the ship workflow by invoking /ship to merge the base branch, run tests, bump VERSION, update CHANGELOG, commit, push, and create a pull request automatically.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate merging a feature branch, running tests, and creating a pull request?

This workflow fetches and merges the base branch into your feature branch, runs the test suite, bumps the semver patch version, updates the changelog from commit diffs, and opens a reviewable pull request.

How does automated changelog generation and version bumping work for git pull requests?

Automated changelog generation works by parsing commit diffs to update the changelog file, while version bumping applies a default micro or patch semver increment before committing and opening the pull request.

Does the automated release workflow stop for failing tests or merge conflicts?

Yes, the automated release workflow stops for complex merge conflicts, major version bumps, and failing critical checks. It handles simple conflicts automatically but halts for triage when tests fail.

Can I use this to split multi-file changes into bisectable commits before opening a PR?

Yes, you can use this to split multi-file changes into bisectable commits. The workflow packages these commits, updates the changelog, and creates a pull request with review readiness info and telemetry.

What is the best way to sync a feature branch with the base branch and verify it with CI?

The best way to sync a feature branch with the base branch and verify it with CI is using an end-to-end automation workflow that fetches the base, runs automated checks, and proceeds to create a PR only when tests pass.