ship

Automate shipping code changes with pre-ship checks, dry-run, execution, verification, and rollback.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill ship-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/ship
Command: npx skills add https://github.com/arbazkhan971/godmode --skill ship-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and enforces a safe, auditable delivery process so teams can reliably move code from branch to PR, release, or production without missing build, test, or security gates.

Core Features & Use Cases

  • Inventory and diff analysis to show what will be shipped and detect secrets or conflict markers.
  • Pre-ship checklist (build, lint, test), dry-run with explicit rollback commands, automated execution, verification, and immediate rollback on failure.
  • Use cases: create and verify PRs, publish releases and tags, run controlled deploys, and monitor post-ship health with clear logging for audits.

Quick Start

Run /godmode:ship to inventory changes, perform pre-ship checks, show a dry-run with rollback plan, and proceed to ship and verify when ready.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate code deployment with pre-ship checks and rollback?

Automate code deployment by running inventory analysis, build, lint, and test gates, followed by a dry-run with an explicit rollback plan before execution. The process verifies post-ship health and logs results to a TSV file for full auditability.

What is a safe release process for pull requests and direct deploys?

A safe release process for pull requests and direct deploys enforces CI gates, scans for secrets and conflict markers, and requires a verified rollback plan. It logs every action to a TSV file to ensure reliable and auditable code delivery.

How do I scan my code changes for secrets and conflict markers before shipping?

Scan code changes for secrets and conflict markers during the initial inventory and diff analysis phase. This pre-ship step detects sensitive data and unresolved merge issues before running build, lint, and test gates.

Can I use automated rollback if my production deployment fails verification?

Yes, automated rollback executes immediately if post-ship verification detects a failure. The system establishes explicit rollback commands during a dry-run phase prior to execution, ensuring quick recovery for applications and services.

Does this shipping workflow require a specific CI pipeline to pass lint and build gates?

No specific CI pipeline is required, but the workflow enforces that lint, build, and test gates must pass before delivery. It applies to existing CI processes for applications and services to ensure changes are safe to ship.

Why do I need a dry-run before executing a direct deploy to production?

A dry-run is needed before executing a direct deploy to generate an explicit rollback plan and verify the inventory diff. It prevents failed deployments by catching issues after CI gates pass but before production changes occur.