production-go

Evaluate release evidence and issue a bounded GO or NO-GO production readiness decision.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill production-go-ravenslight2010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-go
Source: https://github.com/ravenslight2010/Production-run-calculator/tree/main/.agents/skills/production-go
Command: npx skills add https://github.com/ravenslight2010/Production-run-calculator --skill production-go-ravenslight2010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship software based on partial evidence—passing unit tests or a healthy local server—while missing stale generated clients, broken browser-facing workflows, or unresolved security findings. This Skill enforces a fail-closed release decision process that requires current, revision-bound evidence across app health, release gates, security, and operational readiness before recommending publish. ## Core Features & Use Cases - Bounded GO/NO-GO decision: Produces exactly one release decision with a required report covering App health, Release evidence, Security readiness, Operational readiness, and Accepted exceptions. - Evidence gate enforcement: Treats missing, stale, blocked, or unreached gates as unresolved, rejects stale generated API clients, and blocks on unresolved high/critical security findings. - Failure closure and repair fan-out: Records every gate as PASS, FAIL, BLOCKED, NOT REACHED, or MISSING, keeps same-objective repairs in one durable task, and avoids unbounded follow-up task chains. - Use Case: A release manager asks "Can we go live today?" after unit tests pass but browser smoke tests and the security review were never run. The Skill returns NO-GO, names the exact missing evidence, and stops without recommending publish. ## Quick Start Ask the assistant to check whether the app is production-ready and give a GO or NO-GO release status for the current commit.

Frequently Asked Questions about production-go

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

FAQPage Schema
How do I check if my app is production-ready before publishing?

Request a release status assessment for the specific commit. The Skill runs applicable release gates, verifies browser-facing workflows and security readiness, then returns one GO or NO-GO decision with a structured evidence report.

What evidence is required for a GO release decision?

A GO requires passing app health checks, current release gate evidence (typechecks, tests, smoke, accessibility), a clean security review with no unresolved high/critical findings, and explicit answers to operational warnings like rollback and schema changes.

Does a passing local server prove the app is ready to ship?

No. A healthy local process does not prove the browser-facing workflow is healthy. The Skill requires evidence from the artifact-managed web preview and API, including browser results or screenshots, before considering app health passed.

Why did I get NO-GO when all unit tests passed?

Unit tests alone are insufficient. Missing generated-client freshness checks, browser smoke tests, or security review results are treated as MISSING evidence, which is unresolved and forces a NO-GO until the required evidence exists.

Can an accepted exception waive a failed required gate?

No. An accepted exception documents a non-applicable or environment-dependent check with owner, mitigation, and expiry, but it cannot waive a failed required gate, stale generated client, or unresolved high/critical security finding.