shipit

Coordinate multi-repo releases with deterministic plan/apply workflows.

1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/trollefson/shipit --skill shipit-trollefson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipit
Source: https://github.com/trollefson/shipit/tree/main/.claude/skills/shipit
Command: npx skills add https://github.com/trollefson/shipit --skill shipit-trollefson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agent workflows require safe, auditable release orchestration. Shipit guides AI agents through a plan-first release process, coordinating feature-to-dev, dev-to-main promotions, and tagging with deterministic plan files.

Core Features & Use Cases

  • Deterministic plan files that capture commits, target branches, and notes for each release stage.
  • Plan / apply workflow with built-in safety checkpoints, enabling user review before creating PRs/MRs or annotated tags.
  • Multi-repo release coordination, commit enrichment, and centralized release summaries for cross-repo releases.

Quick Start

Install Shipit and run shipit init to initialize your workspace and prepare for a guided release planning session.

Frequently Asked Questions about shipit

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

FAQPage Schema
How do I coordinate multi-repo git releases with AI agents?

Plan-first release orchestration uses deterministic plan files to capture commits and target branches, enabling AI agents to safely coordinate feature-to-dev and dev-to-main promotions across repositories with built-in safety checkpoints.

What is a plan-first git workflow for release orchestration?

A plan-first git workflow separates release planning from execution by generating deterministic plan files that capture commits, target branches, and notes. Users review these plans at safety checkpoints before the system creates pull requests, merge requests, or annotated tags.

How do I automate feature-to-main branch promotions safely?

Feature-to-main branch promotions are automated using a plan and apply workflow with built-in safety checkpoints. The system generates deterministic plan files for user review before creating the pull requests, merge requests, or annotated tags needed for the promotion.

Can I use this release orchestration workflow for multi-repo tagging?

Yes, this release orchestration workflow supports multi-repo tagging workflows. It coordinates cross-repo releases by applying annotated tags through a plan-driven execution model that requires user review at safety checkpoints before finalizing the release.

Do I need YAML frontmatter in SKILL.md to validate AI workflow discovery?

Yes, YAML frontmatter with name and description fields in SKILL.md is required to validate workflow discovery. This ensures the AI agent can correctly identify and execute the deterministic plan and apply workflows for your git releases.

How do I initialize a workspace for AI-assisted git releases?

You initialize a workspace for AI-assisted git releases by running the init command. This prepares your environment for a guided release planning session, setting up the necessary configurations for deterministic plan files and safety checkpoints before executing promotions.