ship

Automate code shipping with base branch merging, tests, and PR creation.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill ship-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill ship-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping code manually is error-prone: developers often skip tests, forget to update changelogs, or push directly to main without review, leading to broken deployments and missing context for team members. This Skill automates the full shipping workflow to enforce best practices and reduce costly mistakes.

Core Features & Use Cases

  • Automated Base Branch Handling: Detects and merges the correct base branch (main/master) before starting the ship process, supporting both GitHub and GitLab platforms.
  • Mandatory Validation Checks: Runs project tests automatically and blocks shipping if tests fail, preventing broken code from reaching production.
  • Automated Release Prep: Bumps the project VERSION file and updates CHANGELOG with recent changes, so release notes are always up to date.
  • Guided PR Creation: Reviews the code diff before opening a pull request, giving you a chance to catch issues before merging.
  • Use Case: A developer finishes a new feature on a feature branch. Running the ship skill handles all post-development steps: merging the latest main, running tests, updating version and changelog, and opening a PR for review, all in one consistent workflow.

Quick Start

Use the ship skill to take your finished feature branch, run all required tests, update the project changelog, and open a pull request to merge your changes into the main branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate code shipping from a feature branch to a pull request?

Automate code shipping by merging the base branch, running tests, bumping versions, updating the changelog, and opening a pull request. This workflow enforces mandatory validation steps to prevent broken code from reaching production.

Why should I automate merge and deployment workflows instead of pushing directly to main?

Automating merge and deployment workflows prevents human errors like skipping tests or forgetting changelog updates. It enforces consistent shipping best practices by requiring test passes and guided pull request creation before any code merge.

Can I deploy code safely if my project tests are currently failing?

You cannot deploy code safely with failing tests using this workflow. Mandatory validation checks automatically run project tests and block the shipping process if any tests fail, ensuring broken code never reaches the main branch.

Does the automated pull request workflow support both GitHub and GitLab?

The automated pull request workflow supports both GitHub and GitLab. It detects and merges the correct base branch from either platform before reviewing the code diff and opening a pull request for team review.

How do I ensure my changelog and version file are updated before creating a pull request?

To ensure changelog and version updates before a pull request, the workflow automatically bumps the project VERSION file and updates the CHANGELOG with recent changes during the shipping process. This keeps release notes consistently up to date.

What is the best way to review a code diff before merging a feature branch?

The best way to review a code diff before merging is using a guided pull request creation process. The workflow reviews the code diff automatically after tests pass, giving you a chance to catch issues before opening the pull request.