meow:shipping

Guide software shipping with ship pipelines, canary deployments, and rollback protocols.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-shipping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meow:shipping
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Ashipping
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-shipping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides concise guidance for ship pipelines, canary deployments, and rollback protocols to streamline releases without invoking full automation.

Core Features & Use Cases

  • Standard ship workflow reference covering pre-ship checks, conventional commits, branch management, PR creation, and rollback planning
  • Canary deployment guidance for high-risk changes, including monitoring criteria and promotion/rollback decisions
  • Rollback templates to document and execute quick reversions during incidents
  • Reference to step-by-step templates and decision matrices to help teams align on release criteria

Quick Start

Use this toolkit to consult release steps on demand and accelerate safe shipping without triggering full automation.

Frequently Asked Questions about meow:shipping

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

FAQPage Schema
What is a canary deployment and when should I use it for production releases?

A canary deployment routes partial traffic to a new version to validate changes before a full rollout. Use this deployment strategy for high-risk changes to monitor specific promotion criteria across staging and canary environments before production promotion.

How do I create a structured deployment workflow with pre-ship checks and PRs?

You can create a structured deployment workflow by following a phased reference covering pre-ship checks, conventional commits, branch management, and PR creation. This standardizes release criteria and aligns your team on safe shipping protocols without triggering full automation.

What should be included in a rollback protocol for production incidents?

A rollback protocol should include templates to document and execute quick reversions during incidents. It needs to cover rollback planning across production, staging, and canary environments to ensure fast recovery when deployment promotion criteria are not met.

Does this shipping reference require any specific deployment automation tools?

No, this shipping reference does not require any specific deployment automation tools or dependencies. It provides concise guidance and step-by-step templates to consult on demand, streamlining releases through phased deployment workflows without invoking full automation.

What are the limitations of using manual references for ship pipelines instead of full automation?

The limitation of using manual references for ship pipelines is that it requires your team to manually execute and monitor the phased deployment workflows, canary conditions, and rollback protocols, rather than relying on automated triggering and decision-making.

How do I decide between canary rollback and production promotion during a release?

You decide between canary rollback and production promotion by evaluating monitoring criteria against pre-defined decision matrices. The reference provides templates to help teams assess canary conditions and determine whether to promote the deployment or execute a rollback plan.