ship

Name: ship
Availability: InStock
Author: everruns

Orchestrate validation, PR creation, CI checks, and merge steps.

42|1|Updated Dec 14, 2025

Search Tags:#git #security #merge #pr #ship #code-review #ci

Ready to run

npx skills add https://github.com/everruns/everruns --skill ship-everruns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/everruns/everruns/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/everruns/everruns --skill ship-everruns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, end-to-end shipping workflow to safely land a requested change and merge only after CI is green, ensuring verifiable evidence and safe branching.

Core Features & Use Cases

Coordinate validation, PR creation, CI checks, and merge steps end-to-end.
Enforce branch safety: never ship from main, keep a clean working tree, rebase onto origin/main, and verify migrations for duplicates.
Capture evidence (diffs, logs, and tests) and update relevant artifacts (specs, docs) to reflect the change.

Quick Start

Initiate a ship workflow for a requested change and guide the agent through validation, PR creation, CI checks, and merge.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I safely merge a PR only after CI checks pass?▼

To safely merge a PR after CI checks pass, you need a goal-oriented shipping workflow that validates changes, verifies CI is green, and captures evidence like diffs and logs before merging. This ensures branch safety and prevents broken builds from landing in the main branch.

What is the best way to automate code review and merge cycles in git?▼

Automating code review and merge cycles in git requires orchestrating validation, PR creation, CI verification, and merge steps end-to-end. A structured shipping workflow enforces branch safety by rebasing onto origin/main and keeping a clean working tree before merging changes.

How do I prevent shipping code changes directly from the main branch?▼

To prevent shipping code changes directly from the main branch, enforce branch safety rules that require working from a separate branch, keeping a clean working tree, and rebasing onto origin/main before attempting to merge. This protects the main branch from unvalidated commits.

Why do I need to verify CI is green before merging a pull request?▼

Verifying CI is green before merging a pull request ensures that automated tests and validations have passed, providing evidence-based confirmation that the changes are safe. This workflow prevents unverified or broken code from landing in the main branch.

Can I update specs and docs automatically when merging code changes?▼

You can update specs and docs automatically during the shipping workflow by capturing validation evidence and selectively updating relevant artifacts to reflect the change. This ensures documentation stays synchronized with the landed code.

What steps are needed to validate migrations before merging a git PR?▼

Validating migrations before merging a git PR involves checking for duplicates and running end-to-end smoke tests within the shipping workflow. This verification happens alongside CI checks and branch rebasing to ensure safe changes merge only after CI is green.