Agent skill · DevOps & Cloud

pre-ship-gate

A ship gate that runs before any production deploy: checks the silent failure modes that make a deploy 'succeed' while prod stays broken, then verifies the live revision instead of trusting deploy output.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill pre-ship-gate --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Declared author: Sharrmavishal
Path: skills/pre-ship-gate/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Pre-Ship Gate ## Overview Most bad deploys do not fail loudly. The pipeline goes green, the CLI prints "deployed", and the old or broken version is still what users hit. This skill is the gate you run right before a production deploy and right after, so an agent stops trusting deploy output and starts confirming what is actually live. It exists because "the deploy command exited 0" and "the new version is serving traffic" are two different facts, and agents routinely confuse them. ## When to Use This Skill - Use before running any command that pushes to a production or staging environment. - Use when an agent is about to report "shipped", "deployed", or "live". - Use when a deploy reported success but users still see the old behavior. - Use when a release involves database migrations, feature flags, or a staged rollout. ## How It Works The gate has three phases. Do not skip to phase 3. ### Phase 1: Pre-flight (before the deploy runs) Walk the silent failure catalog. These are the modes that let a deploy "succeed" while production stays broken. For each one, confirm it or flag it. Do not assume. - **Migrations**: Are schema migrations part of this release, and will they run agains

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. How It Works
  4. Phase 1: Pre-flight (before the deploy runs)
  5. Phase 2: Run the deploy
  6. Phase 3: Verify live (before saying "shipped")
  7. Examples
  8. Example 1: Verifying the live revision instead of trusting the deploy log
  9. Example 2: Pre-flight verdict format an agent can emit
  10. Best Practices
  11. Limitations
  12. Common Pitfalls
  13. Security & Safety Notes
  14. Related Skills
Commands it runs
You intended to ship this commit
Ask the running service what it is actually serving
if [ "$INTENDED" = "$LIVE" ]; then
echo "Live revision $LIVE matches intended $INTENDED: verified shipped."
else
echo "MISMATCH: intended $INTENDED but live is $LIVE. Do not report shipped."
fi
More from agentic-awesome-skills
All skills →
About this skill
What does the pre-ship-gate skill do?

A ship gate that runs before any production deploy: checks the silent failure modes that make a deploy 'succeed' while prod stays broken, then verifies the live revision instead of trusting deploy output.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill pre-ship-gate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going