skills.rest
anilveersingh1308
anilveersingh1308COMMUNITY
Explore all skills by this author →
GitHub

gstack-ship

Run tests, bump VERSION, update CHANGELOG, and open a PR.

Updated May 19, 2026
Search Tags:#testing#deployment#release automation#ship#version bump#github pull request#changelog update
One-click install
npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-ship-anilveersingh1308
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-ship
Source: https://github.com/anilveersingh1308/copilot-skills/tree/main/.github/skills/gstack-ship
Command: npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-ship-anilveersingh1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken releases by turning a vague “ship it” moment into a structured, repeatable workflow that finds the right merge base, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, and creates the PR safely instead of doing ad hoc pushes.

Core Features & Use Cases

  • Automated ship workflow orchestration: Detects the correct base branch, runs the expected test suite, and prepares a clean merge by handling the usual release steps in order. Use it when you are ready to deploy and want the release process to be consistent every time across branches.
  • Diff review-driven readiness: Performs a review of the changes so the resulting PR is reviewed as part of “shipping,” reducing the chance of surprises for reviewers and downstream automation. Use it when “the code is ready” but you want a diff-focused sanity pass before a PR exists.
  • Release bookkeeping with VERSION and CHANGELOG: Bumps VERSION, updates CHANGELOG, and commits those changes along with the tested code so release history stays accurate. Use it for routine releases where you need both code and metadata aligned for the team.

Quick Start

Tell your AI assistant: “Please gstack-ship, I’m ready to ship and want a PR with tests and changelog updates.”

Frequently Asked Questions about gstack-ship

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

FAQPage Schema
How do I automate version bump, changelog updates, and PR creation for a release?▼

Release automation orchestrates the full ship workflow by detecting the merge base, running tests, bumping VERSION, updating CHANGELOG, committing, pushing, and opening a PR. This ensures release bookkeeping and code changes are aligned consistently across branches without ad hoc pushes.

What is the best way to run tests and review diffs before pushing to main?▼

Diff review-driven readiness runs the test suite and performs a review of changes before creating a PR. This sanity pass reduces surprises for reviewers by ensuring the code is tested and reviewed as part of the shipping process, rather than pushing unverified commits directly to main.

Can I use release automation to prepare a pull request from a development branch?▼

Yes, release automation detects the correct base branch from your development branch and prepares a clean merge. It handles the release steps in order, including committing and pushing the tested code, then opens a PR to safely merge your changes.

Does the ship workflow require manual decisions during the pull request process?▼

The ship workflow uses interactive gates to prompt for any required decisions during the pull request process. It operates safely in plan mode with allowed tool actions, ensuring you can proactively confirm readiness cues and handle decisions before committing and pushing changes.

When should I not use an automated ship workflow for deployment?▼

You should avoid using an automated ship workflow for deployment if your project lacks a VERSION file or CHANGELOG, as the process specifically bumps and updates these files. It is designed for routine, structured releases rather than ad hoc pushes or environments without standard release bookkeeping.

How does gstack-ship handle merge base detection for GitHub pull requests?▼

gstack-ship handles merge base detection by automatically identifying the correct base branch for your GitHub pull request. This prevents broken releases by ensuring tests and diffs are evaluated against the right branch before version bumping and changelog updates are committed and pushed.

Related Skills

Explore More Software Engineering Skills→
fghaffarfghaffar

ship

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

Community
Advanced
devopstalesdevopstales
1

ci-cd-and-automation

Automate CI/CD pipeline setup, testing, and deployment with GitHub Actions.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
23000311472300031147

ship

Coordinate ship workflows from base-branch detection to PR creation.

Community
Advanced