ship

Automate end-to-end release workflows by merging, testing, and creating PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automates the end-to-end release workflow by merging the base branch, running tests, reviewing diffs, bumping version, updating changelog, committing, pushing, and creating a PR—triggered by a user command.

Core Features & Use Cases

  • End-to-end release automation: merge base, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Manual trigger: invoked via /ship to give you control over when releases happen.
  • CI/CD integration: coordinates with your existing pipelines to ensure consistent releases across environments.

Quick Start

Type /ship to trigger the full release workflow from your 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 a git release workflow from a feature branch?

To automate a git release workflow, you can trigger an end-to-end process that merges the base branch, runs tests, bumps the version, updates the changelog, and opens a pull request. This ensures consistent, auditable releases.

What is the best way to merge the base branch, run tests, and create a PR automatically?

The best way to merge the base branch, run tests, and create a PR automatically is to use a command-driven release workflow that reviews diffs and coordinates with your existing CI/CD pipelines to produce auditable releases.

Does this release automation tool work with my existing CI/CD pipelines?

Yes, this release automation tool integrates with your existing CI/CD pipelines to coordinate consistent releases across environments. It automates merging, testing, version bumping, and PR creation within your current setup.

How do I trigger an end-to-end pull request release with version bumping and changelog updates?

You trigger an end-to-end pull request release by invoking the manual /ship command from your feature branch. This initiates the workflow to bump the version, update the changelog, commit, push, and open a PR.

Do I need git and test results to automate my deployment workflow?

Yes, you need access to git, test results, version tooling, and changelog management to automate your deployment workflow. The process relies on these components to execute diffs review, commit, push, and PR creation.

When should I not use an automated PR workflow for my releases?

You should not use an automated PR workflow when you need manual control over individual file commits or when your deployment process bypasses standard pull request driven workflows for direct main branch pushes.