Production Audit

This gives you a pre-launch production readiness check that runs locally instead of sending your repo to a third-party service. It walks through auth boundaries, webhook idempotency, migration rollback paths, and the deployment surface you actually shipped, then scores whether you're clear to deploy or still have blockers. The lens is practical triage, like asking a senior engineer to spot what breaks in prod before you find out the hard way. It's built for that moment when CI is green but you want eyes on the real risks: are secrets leaked, can you roll back, will duplicate Stripe webhooks charge twice. Not a compliance audit, just engineering common sense encoded into a repeatable checklist.

skills.sh installs: 5.7K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill production-audit --agent claude-code

Installs into .claude/skills of the current project.

Files

Production Audit

Use this skill when the user asks whether an application is ready to ship, what could break in production, or what must be fixed before a launch. This is a maintainer-safe rewrite of the stale community production-audit idea: it keeps the useful production-readiness lens and removes unpinned external execution and third-party data sharing.

When to Use

The user asks "is this production-ready", "what would break in prod", "what did we miss", "audit this repo", or "ready to ship?"
A feature was merged and needs a pre-deploy or post-merge risk pass.
A public launch, demo, customer rollout, or investor walkthrough is close.
CI is green but the user wants production risk, not only test status.
A deployed URL, release branch, PR, or current checkout is available for evidence gathering.