skills.rest
psyche911
psyche911COMMUNITY
Explore all skills by this author →
GitHub

ship

Automates Git release workflows from merge to PR creation.

Updated Jan 18, 2026
Search Tags:#automation#workflow#versioning#ci-cd#ship#pull-request
One-click install
npx skills add https://github.com/psyche911/investor-council-app --skill ship-psyche911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/psyche911/investor-council-app/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/psyche911/investor-council-app --skill ship-psyche911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow automates the entire release lifecycle in a Git-based project, removing manual steps from merging, testing, versioning, and PR creation.

Core Features & Use Cases

  • Fully automated release pipeline: merges the feature branch, runs tests, reviews diffs, bumps VERSION, updates CHANGELOG, commits, pushes, and creates a PR.
  • Pre-merge gate behavior: validates on-branch status and handles conflicts automatically where possible; aborts on critical issues.
  • PR-centric delivery: outputs the PR URL upon completion for quick stakeholder access and traceability.
  • Use Case: On a feature branch, trigger the ship workflow to publish a PR that merges into main after successful tests and documentation updates.

Quick Start

Run the /ship command on a feature branch to execute the complete release workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate Git release workflows from a feature branch to a pull request?▼

Automating Git release workflows involves merging a feature branch, running tests, bumping the VERSION, updating the CHANGELOG, and generating a pull request URL on the target branch.

What is an end-to-end release automation pipeline for version control?▼

End-to-end release automation manages the full lifecycle from feature branch merging and testing to version bumping, changelog updates, and pull request creation.

Do I need a local shell environment and network access to automate pull request creation?▼

Yes, automating pull request creation requires a Git workspace with the main branch tracked, a shell environment to execute commands, and network access to push commits.

How do CI-CD release pipelines handle on-branch conflicts before merging to main?▼

Automated release pipelines handle on-branch conflicts by validating branch status, resolving conflicts automatically where possible, and aborting the workflow on critical issues.

Can I automatically update the changelog and version number during a Git pull request release?▼

Yes, you can automatically update the changelog and bump the version number during a release by triggering an automated workflow that reviews diffs and commits changes before pushing.

When should I not use an automated release workflow for feature branch publishing?▼

You should avoid automated release workflows when your feature branch has critical unresolved conflicts, lacks a tracked main branch, or operates in an environment without shell or network access.

Related Skills

Explore More Software Engineering Skills→
andymaiandymai
20

pr-workflow

Automate pull request workflows with AI review gates and GitHub releases.

Community
Advanced
DisentinelDisentinel
36

/approve — Push PR to Auto-Merge

Push a feature branch, create a GitHub pull request, and enable auto-merge.

Community
Advanced
sjevsjev
1

merge

Merges a feature branch into the base branch using a commit.

Community
Intermediate
ajsai47ajsai47
11

ship

Automate end-to-end code shipping with merging, tests, versioning, and PRs.

Community
Advanced