Ship Gate
A structured go/no-go gate before a change ships, so every release passes the same checks.
Before & after
Same prompt, same agent — the only difference is the skill.
Before you deploy, there are several things you should verify. Your tests should be passing, and you'd want to make sure your changes don't break existing functionality. You should review the diff to catch any obvious issues. Check that you haven't accidentally committed debug code or secrets. Verify that dependencies are properly updated. Make sure rollback procedures are documented. It helps to have a checklist so nothing gets missed. What's the scope of your deployment?
PRE-SHIP CHECKLIST TEST VERIFICATION OK: Unit tests passing: 245/245 OK: Integration tests passing: 12/12 OK: E2E tests passing: 8/8 (checkout flow, auth, main user paths) OK: Coverage delta: 82% maintained (no regressions) Status: PASS CODE REVIEW OK: Diff reviewed: 1,240 lines, 8 files OK: No debugging code (console.log, debugger statements) OK: No hardcoded secrets or API keys OK: No large assets committed Status: PASS DEPENDENCY CHECK OK: package.json updated OK: npm audit clean (zero critical vulnerabilities) OK: Breaking changes reviewed (3 minor bumps, no breaking) OK: Migrations run on staging successfully Status: PASS SECURITY GATE OK: Authentication logic unchanged OK: Authorization checks in place (user ID validation, role checks) OK: No new SQL queries (uses ORM consistently) OK: CORS headers correct (no overly permissive settings) Status: PASS PERFORMANCE CHECK OK: Page load time stable (±2% variance) OK: Database queries optimized (index scan verified) OK: No new N+1 queries introduced Status: PASS ROLLBACK READINESS OK: Rollback procedure documented: revert to commit abc123d OK: Database migration reversible: down migration tested OK: Cache invalidation plan: Redis keys to clear on rollback Status: READY FINAL SIGN-OFF Deployed by: Sarah Chen Deploy time: 2026-07-31 14:32 UTC Expected propagation: 5 minutes Monitoring: Alert on error spike, latency increase, auth failures ALL GATES PASSED. READY FOR PRODUCTION.
About this skill
name: ship-gate description: Use when Structured Claude skill that gives Claude a repeatable workflow for ship gate.
Ship Gate
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Ship Gate workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the ship-gate skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Ship Gate; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: ship-gate
description: Use this skill as a pre-release checklist that gives a repeatable go/no-go workflow before shipping a change.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Ship Gate
Runs a structured go/no-go gate before a change ships, so releases pass through the same checks every time instead of an ad hoc final look.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.