skills.rest
TimHL5
TimHL5COMMUNITY
Explore all skills by this author →
GitHub

ship

Merge base branches, run tests, update versioning, and open PRs.

Updated Mar 21, 2026
Search Tags:#automation#git#versioning#release#ci-cd#ship#pull-request
One-click install
npx skills add https://github.com/TimHL5/carousel --skill ship-timhl5
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/TimHL5/carousel/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/TimHL5/carousel --skill ship-timhl5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation streamlines the end-to-end release workflow by handling base-branch merges, tests, version bumps, changelog updates, commits, pushes, and PR creation. It reduces manual toil and helps teams ship more reliably.

Core Features & Use Cases

  • Base-branch merge + test orchestration: Merges the latest base into the feature branch and runs the full test suite.
  • Versioning and changelog automation: Bumps the VERSION, updates CHANGELOG, and commits the changes.
  • PR generation and deployment hints: Creates a PR and offers proactive deployment prompts when appropriate.
  • Conflict handling: Detects and resolves simple conflicts automatically; surfaces complex conflicts for manual resolution.
  • Proactive shipping: Suggests shipping when code is ready and deployment is viable.

Quick Start

Trigger the ship workflow on your feature branch to start the automated release.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my git release workflow from feature branch to pull request?▼

Release automation handles the end-to-end workflow by merging the base branch into your feature branch, running tests, updating versioning and changelog, then committing, pushing, and opening a pull request automatically.

How does automated versioning and changelog updates work during a release?▼

Automated versioning bumps the VERSION file and updates the CHANGELOG with new entries, then commits these changes directly to your feature branch before pushing and generating a pull request.

Can I automate base branch merges and test suite orchestration in my CI/CD pipeline?▼

Yes, you can automate base branch merges and test suite orchestration in your CI/CD pipeline to ensure deterministic releases by merging the latest base into your feature branch and running the full test suite before proceeding.

How are merge conflicts handled during automated pull request creation?▼

Conflict handling during automated pull request creation detects and resolves simple conflicts automatically, while surfacing complex conflicts for manual review to ensure safe operations and prevent faulty merges.

What is the best way to get proactive deployment hints before opening a pull request?▼

Proactive deployment hints are generated automatically after tests pass and versioning updates, suggesting when code is ready and deployment is viable before the final pull request is created and pushed.

When should I not use end-to-end release automation for my software project?▼

You should avoid end-to-end release automation when your software project requires complex conflict resolution that cannot be handled automatically, as the workflow surfaces these conflicts for manual review instead of forcing a merge.

Related Skills

Explore More Software Engineering Skills→
jambolojambolo

new-rust-project

Initialize Rust projects with cargo, git, and GitHub Actions CI/CD.

Community
Advanced
gsarmaonlinegsarmaonline

review-comments

Analyze pull request review comments and resolve failing GitHub Actions checks.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
ajsai47ajsai47
11

ship

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

Community
Advanced