ship

Create PRs, run CI checks, deploy builds, and verify production with rollback.

204|14|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/garagon/nanostack --skill ship-garagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/garagon/nanostack/tree/main/ship
Command: npx skills add https://github.com/garagon/nanostack --skill ship-garagon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It moves code from "done" to verified production in a single, safety-guarded flow, removing uncertainty around PR creation, CI failures, deployments, and post-deploy verification.

Core Features & Use Cases

  • Pre-flight and quality checks: automated hygiene and secret scanning before exposing changes.
  • Controlled PR workflow: mandatory PR preview, templated PR creation, and CI monitoring until green.
  • Post-merge verification and rollback: smoke tests, deploy log checks, metrics review, artifact saving, and a documented revert plan.
  • Use Case: ship a bugfix or small feature by preparing a focused PR, watching CI, verifying the staging/production behavior, and reverting quickly if something breaks.

Quick Start

Run /ship to perform pre-flight checks, present a PR preview for approval, create the PR, monitor CI, verify the deployment, and save the release artifact.

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 from a PR to production?

Automate code deployment by creating a structured PR, monitoring CI checks until green, deploying builds, and executing post-deploy verification. This safety-guarded flow removes uncertainty by moving code from a development branch to verified production.

What is the best way to ensure a safe rollback after a release?

Ensure a safe rollback after a release by executing deterministic revert plans and post-deploy smoke tests. The workflow includes deploy log checks, metrics review, and artifact saving to quickly revert if production behavior breaks.

How does CI monitoring work during a GitHub PR release pipeline?

CI monitoring during a GitHub PR release pipeline tracks continuous integration status until all checks are green. It runs pre-flight quality and secret scanning, presents a PR preview for approval, and saves release artifacts after deployment.

Can I use this deployment workflow for git-based projects without external dependencies?

Yes, you can use this deployment workflow for git-based projects without external dependencies. It is compatible with GitHub CLI and local helper scripts, applying to projects where changes require review, CI testing, and staging or production validation.

What pre-flight checks are needed before creating a PR for production deployment?

Pre-flight checks needed before creating a PR include automated hygiene validation and secret scanning. These checks run before exposing changes to ensure code quality and prevent sensitive data leaks during the release pipeline.