ship

Automate the end-to-end ship workflow from merge to PR creation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Faeif/linguaquest --skill ship-faeif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Faeif/linguaquest/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/Faeif/linguaquest --skill ship-faeif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing code is error-prone and manual: merging the base branch, running tests, updating the VERSION, bumping the CHANGELOG, committing, pushing, and creating a PR. This skill streamlines the end-to-end release workflow to reduce mistakes and speed up shipping.

Core Features & Use Cases

  • Automates base-branch detection and merge, triggering tests and checks.
  • Bumps the VERSION, updates the CHANGELOG, commits changes, and pushes to a PR branch.
  • Creates and routes a PR for review, coordinating release gates and deployments when approved.
  • Use case: when a feature is ready and needs a clean, auditable release cycle with clear traceability.

Quick Start

Say "ship it" when your code is ready to release and want to push through a PR-based release flow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a PR-based release workflow with version bumping and changelog updates?

You can automate a PR-based release workflow by triggering this Skill to merge the base branch, run tests, bump the VERSION, update the CHANGELOG, commit, push, and open a pull request for review.

What is the best way to ensure release hygiene before creating a pull request?

The best way to ensure release hygiene is to coordinate review gates by automatically reviewing diffs, running tests, and bumping the VERSION and CHANGELOG deterministically before pushing code to a PR branch.

Do I need any specific CI-CD components configured to use this release flow?

No specific CI-CD components or dependencies are required. The Skill independently detects the base branch, runs tests, updates the VERSION and CHANGELOG, and prepares deploy readiness without external components.

How does a PR-based release cycle handle changelog generation and version updates?

This PR-based release cycle handles changelog generation and version updates by automatically bumping the VERSION file and updating the CHANGELOG during the commit phase before pushing the changes to a PR branch.

Can I use this automated release flow for any git repository ready to ship code?

Yes, you can use this automated release flow for any git repository ready to ship code. It streamlines the end-to-end workflow from base branch merge to PR creation, ensuring clean and auditable release traceability.