ship

Prepare feature branches for release with tests, versioning, and pull requests.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill ship-geneducation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/ship
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill ship-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the busywork and risk from getting finished code out the door. It checks the branch, runs the right verification steps, and turns a ready change into a clean release path.

Core Features & Use Cases

  • Release workflow: Detects the base branch, reviews the diff, and checks recent commits before shipping.
  • Verification and cleanup: Runs tests, updates versioning, refreshes the changelog, and catches release blockers early.
  • Commit, push, and PR creation: Packages the work into a commit, pushes it, and opens the pull request instead of leaving the user to stitch the last mile together.
  • Use case: A feature is done, the branch is dirty, and the user wants the safest path to merge it without forgetting release steps.

Quick Start

Ask the ship skill to prepare the branch for release, run verification, update release files, and create the pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I prepare a feature branch for a pull request and release?

To prepare a feature branch for a pull request, validate the branch, review the diff, and run verification steps. This workflow turns a ready change into a clean release path by ensuring branch validation and review-aware safeguards.

What steps are needed to update version and changelog before pushing code?

Updating version and changelog before pushing code requires running tests, applying version bumps, and refreshing the changelog. This process catches release blockers early and packages the work for deployment readiness.

How does branch management work when shipping code to a mergeable state?

Branch management for shipping code works by detecting the base branch, reviewing recent commits, and applying release safeguards. This mechanism ensures the feature branch reaches a mergeable release state.

Do I need to run tests before creating a pull request for a deployment?

Yes, you need to run tests before creating a pull request for deployment. Test execution is a required verification step to catch release blockers early and ensure repository changes are safe to ship.

What is the safest way to ship code from a dirty branch without forgetting release steps?

The safest way to ship code from a dirty branch is to automate branch validation, diff review, test execution, and changelog updates. This approach removes the risk by coordinating deployment readiness and opening the pull request.