production-audit

Audits repository evidence to score production readiness before launch or deployment.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/malinovskiy-makar/qls --skill production-audit-malinovskiy-makar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-audit
Source: https://github.com/malinovskiy-makar/qls/tree/main/.claude/skills/production-audit
Command: npx skills add https://github.com/malinovskiy-makar/qls --skill production-audit-malinovskiy-makar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often mistake green CI for production readiness and ship with hidden risks like non-idempotent webhooks, missing rollback paths, or exposed secrets. This Skill performs a local-evidence audit of your repo and deployment surface to answer "what breaks in prod?" without sending code to external services. ## Core Features & Use Cases - Evidence-Based Scoring: Produces a 0-100 readiness score with bands (Blocked, Risky, Launchable With Caveats, Strong) and hard caps for critical gaps like missing auth or non-idempotent payment webhooks. - Structured Risk Lenses: Systematically inspects security and auth, data integrity, payments and webhooks, operations, and user experience boundaries that actually exist in the repo. - Privacy-Safe Auditing: Uses only local git history, CI configs, migrations, and user-authorized checks, never uploading source or secrets to third-party scanners. - Use Case: Before a public launch, ask whether your app is ready to ship and receive a score, a list of blockers, high-value fixes, evidence checked, and one concrete next action. ## Quick Start Ask the assistant to audit this repository for production readiness and tell you what would break in production before launch.

Frequently Asked Questions about production-audit

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 launch?

Run a production readiness audit that inspects git history, CI workflows, migrations, auth boundaries, webhooks, and rollback paths. The audit returns a 0-100 score with blockers and high-value fixes ranked by launch risk.

What does a production readiness audit check in a repository?

It checks package scripts, CI workflows, Docker files, API routes, auth middleware, database migrations, environment variable validation, health checks, webhook idempotency, and rollback documentation. It also reviews launch-critical user paths on desktop and mobile.

Does the production audit send my code to an external service?

No, the audit runs entirely on local and user-authorized evidence such as git commands and repo files. External scanners or remote tools are only used if you explicitly approve that specific tool and data flow.

When should I not use a production readiness audit?

Skip it during active implementation when line-level secure coding review is more appropriate, for docs-only repos or libraries without a runtime surface, and when you need formal legal or regulatory compliance certification rather than engineering triage.

Why is green CI not enough to ship to production?

Green CI only proves tests pass, not that webhooks are idempotent, migrations have rollback paths, secrets stay out of client bundles, or auth is enforced server-side. The audit caps scores when these launch-critical gaps exist despite passing CI.