ship

Automate the end-to-end ship workflow from base branch detection to PR creation.

4|1|Updated Sep 13, 2023
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill ship-louisfghbvc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/ship
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill ship-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end ship workflow: detect and merge the base branch, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and create a PR. It also promotes proactive invocation when the user asks to deploy, push, or create a PR, but never pushes or PRs directly without user intent.

Core Features & Use Cases

  • Base-branch detection and merge prep to ensure you ship from the correct target.
  • Automatic test execution and result review to catch regressions early.
  • Version bump, CHANGELOG update, commit, and PR creation to streamline releases.
  • Proactive invocation for deployment-related requests, reducing manual steps when you’re ready to ship.

Quick Start

Run the ship workflow on your feature branch to auto-detect the base, run tests, update the version and changelog, commit, push, and open 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 the git pull request workflow with version bumps and changelog updates?

Automating the git pull request workflow involves detecting the base branch, merging it, running tests, bumping the VERSION, updating the CHANGELOG, and pushing to create a PR. This ensures pre-merge checks pass before deployment.

What's the best way to create a PR and update the changelog at the same time?

The best way to create a PR and update the changelog simultaneously is using an end-to-end ship workflow that automatically reviews diffs, bumps the VERSION, updates the CHANGELOG, commits, and pushes the feature branch.

Does the automated ship workflow push code or create a PR without user intent?

No, the automated ship workflow never pushes or creates a PR without explicit user intent. It proactively suggests deployment when asked but requires user confirmation before pushing code to the remote repository.

How do I prepare a feature branch for deployment before creating a pull request?

To prepare a feature branch for deployment, you detect the base branch, merge it into your feature branch, and run tests to catch regressions. This ensures your branch is ready for a fully automated PR handoff.

What happens if there are merge conflicts when merging the base branch?

If there are merge conflicts or base-branch issues during the merge step, the ship workflow aborts automatically. This safeguard prevents pushing incompatible code and ensures CI results remain valid before PR creation.

Can I run tests and review diffs automatically before bumping the version?

Yes, you can run tests and review diffs automatically before bumping the version. The deterministic ship workflow sequence executes tests and diff reviews first, aborting if checks fail, then proceeds to version bumping.