skills.rest
kinetas
kinetasCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automates the complete ship workflow from base-branch detection to PR creation.

Updated Mar 11, 2026
Search Tags:#automation#changelog#pr#ci-cd#ship#tests#version-bump
One-click install
npx skills add https://github.com/kinetas/ai_coding_web --skill ship-kinetas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/kinetas/ai_coding_web/tree/main/gstack/ship
Command: npx skills add https://github.com/kinetas/ai_coding_web --skill ship-kinetas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and automate the complete shipping process from base-branch detection through PR creation. It eliminates manual handoffs and reduces drift between code readiness and deployment readiness.

Core Features & Use Cases

  • Detects the base branch, runs tests, reviews diffs, bumps VERSION, updates CHANGELOG, commits, pushes, and creates PRs.
  • Works across typical shipping scenarios when asked to "ship", "deploy", or "push to main".
  • Keeps a consistent, auditable process that can be traced through commit messages and PRs.

Quick Start

Run the ship workflow by issuing the /ship command to start the automated shipping process.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my end-to-end ship workflow from running tests to creating a PR?▼

Automating an end-to-end ship workflow involves detecting the base branch, running tests, reviewing diffs, bumping the version, updating the changelog, committing, pushing, and creating a PR in a single coordinated process.

What is the best way to coordinate version bumps and changelog updates before pushing to main?▼

The best way to coordinate version bumps and changelog updates is using an automated shipping process that applies conventional versioning and changelog conventions before committing and pushing a ready-to-merge branch.

Does automated shipping work with standard CI-CD scenarios and conventional versioning?▼

Automated shipping works across standard CI-CD scenarios by relying on automated tests and conventional versioning to detect the base branch, review diffs, and produce a ready-to-merge branch with an updated changelog.

Can I start the ship workflow with a single command to push code to main?▼

You can start the ship workflow by issuing a single command to trigger the automated shipping process, which handles everything from base-branch detection to PR creation for pushing code to main.

Why do I need to run tests and review diffs before bumping a version in my deployment workflow?▼

Running tests and reviewing diffs before a version bump ensures code readiness and eliminates manual handoffs, reducing drift between code readiness and deployment readiness in your deployment workflow.

What are the limitations of automating PR creation and changelog updates without conventional commits?▼

Without conventional commits, automating PR creation and changelog updates lacks the standardized commit messages needed for consistent traceability and auditable process tracking across typical shipping scenarios.

Related Skills

Explore More Software Engineering Skills→
lemiglemig

ship

Orchestrate software shipping from base-branch detection to PR creation.

Community
Intermediate
ajsai47ajsai47
11

land-and-deploy

Merge GitHub pull requests and verify production health after deployment.

Community
Advanced
bennybennisonbennybennison

verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Community
Intermediate
umairinayatumairinayat
5

ship

Automate merge, test, version bump, changelog update, and PR creation for Git releases.

Community
Advanced