verify-before-ship

Enforce a 7-gate production safety checklist with evidence before deployment.

100|15|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/rfxlamia/skillkit --skill verify-before-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-before-ship
Source: https://github.com/rfxlamia/skillkit/tree/main/skills/verify-before-ship
Command: npx skills add https://github.com/rfxlamia/skillkit --skill verify-before-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces a rigorous 7-gate verification process before any code is deployed to production, preventing costly mistakes and ensuring stability.

Core Features & Use Cases

  • Mandatory Safety Gates: Enforces 7 non-negotiable production safety gates.
  • Evidence-Based Verification: Requires concrete evidence for each gate, not just statements.
  • Rationalization Countermeasures: Actively identifies and blocks common excuses for skipping checks.
  • Use Case: Before merging a critical bug fix or deploying a new feature, this Skill ensures all tests pass, security scans are clean, rollback plans are documented, and code reviews are approved, guaranteeing a safe release.

Quick Start

Use the verify-before-ship skill to confirm all 7 production safety gates are cleared with evidence before deploying.

Frequently Asked Questions about verify-before-ship

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

FAQPage Schema
How do I enforce production safety gates before a deployment?

Production safety gates are enforced by requiring explicit evidence artifacts for tests, security scans, change validation, environment configuration, staging verification, rollback planning, and code review approval before any deployment proceeds.

What should be verified before deploying code to production?

Before deploying code to production, you must verify passing tests, clean security scans, validated changes, correct environment configuration, successful staging verification, documented rollback plans, and approved code reviews with concrete evidence artifacts.

How do I stop developers from skipping CI/CD quality checks under time pressure?

To stop developers from skipping CI/CD quality checks, implement rationalization countermeasures that actively identify and block common excuses for bypassing quality assurance procedures, ensuring all safety gates pass with evidence.

Does evidence-based deployment verification require specific CI/CD pipeline tools?

Evidence-based deployment verification does not require specific CI/CD pipeline tools, as it focuses on validating concrete evidence artifacts across seven safety gates rather than mandating particular pipeline platforms or external dependencies.

Can I use automated quality gates for critical bug fixes in production?

Automated quality gates can be used for critical bug fixes in production by enforcing the same seven non-negotiable safety checks, ensuring that urgent fixes do not bypass tests, security scans, staging verification, or rollback planning.

What are the limitations of rationalization countermeasures in deployment safety?

The limitation of rationalization countermeasures in deployment safety is that they specifically target and block common excuses for skipping checks, meaning they require explicit evidence artifacts for each gate and cannot process deployments lacking concrete validation proof.