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.
When Not to Use
- During active implementation when the right lens is line-level secure coding;
use
security-review first.
- For pure libraries, templates, docs-only repos, or scaffolds unless the user
wants packaging/release readiness rather than application readiness.
- When the user asks for a formal compliance audit. This skill is engineering
triage, not legal, financial, medical, or regulatory certification.
- When the only available evidence is a product idea with no repo, deployment,
CI, or runtime surface.
How It Works
Build the audit from local and user-authorized evidence. Do not run unpinned
remote code, upload repository contents to third-party services, or call
external scanners unless the user explicitly approves that specific tool and
data flow.
Use this order:
- Establish the release surface.
- Read recent changes and current branch state.
- Inspect runtime, auth, data, payment, background-job, AI, and deployment
boundaries that actually exist in the repo.
- Check CI, tests, migrations, environment documentation, and rollback path.
- Produce a short ship/block recommendation with specific fixes.
Evidence Checklist
Start with cheap, local signals:
git status --short --branch
git log --oneline --decorate -20
git diff --stat origin/main...HEAD
Then inspect the project-specific surface:
- Package scripts, CI workflows, release scripts, Docker files, and deployment
manifests.
- API routes, webhooks, auth middleware, background workers, cron jobs, and
database migrations.
- Environment variable documentation and startup checks.
- Observability hooks, error reporting, logs, health checks, and dashboards.
- Rollback, seed, migration, and backfill instructions.
- E2E coverage for the user paths that matter most.
If a deployed URL is in scope, use browser or HTTP checks only against that URL
and avoid credentialed actions unless the user supplies a safe test account.
Risk Lenses
Security And Auth
- Are public routes, API routes, and admin routes clearly separated?
- Are auth and authorization enforced server-side?
- Are secrets kept out of client bundles, logs, example output, and checked-in
files?
- Are rate limits, CSRF protections, CORS policy, and upload validation present
where the app needs them?
- Does the AI or agent surface defend against prompt injection, tool abuse, and
untrusted content crossing into privileged actions?
Data Integrity
- Do migrations run forward cleanly and have a rollback or recovery plan?
- Are destructive migrations, backfills, and data imports staged safely?
- Do database policies, grants, and service-role boundaries match the app's
tenancy model?
- Are retries idempotent for writes, jobs, and webhook handlers?
Payments And Webhooks
- Are webhook signatures verified before parsing trusted payload fields?
- Is each payment, subscription, or fulfillment webhook idempotent?
- Are replay, duplicate delivery, and out-of-order delivery handled?
- Are test-mode and live-mode credentials separated?
Operations
- Can the app start from a clean checkout using documented commands?
- Are required environment variables named, validated, and fail-fast?
- Is there a health check that proves dependencies are reachable?
- Are deploy, rollback, and incident-owner paths documented?
- Are logs useful without leaking secrets or personal data?
User Experience
- Are the launch-critical paths covered on desktop and mobile?
- Are forms usable on mobile without input zoom, layout overlap, or blocked
submission states?
- Do loading, empty, error, and permission-denied states tell the user what
happened?
- Is there a support or recovery path when a critical operation fails?
Scoring
Use scores to force prioritization, not to imply mathematical certainty.
| Band |
Score |
Meaning |
| Blocked |
0-49 |
Do not ship until the top risks are fixed |
| Risky |
50-69 |
Ship only behind a small rollout or internal beta |
| Launchable With Caveats |
70-84 |
Ship if owners accept the listed risks |
| Strong |
85-100 |
No obvious launch blockers from available evidence |
Cap the score at 69 if any of these are true:
- Authentication or authorization is missing on sensitive data.
- Payment or fulfillment webhooks are not idempotent.
- Required migrations cannot be run safely.
- Secrets are exposed in client bundles, logs, or committed files.
- There is no rollback path for a high-impact release.
Cap the score at 84 if CI is not green or the launch-critical path was not
tested end to end.
Output Format
Lead with one sentence:
Production audit: 76/100, launchable with caveats, with webhook idempotency and rollback docs as the two risks to fix before public launch.
Then list:
Blockers: must-fix items before deploy.
High-value fixes: next fixes if the user wants to improve the score.
Evidence checked: files, commands, CI, deployed URL, or PRs inspected.
Evidence missing: what would change confidence if provided.
Next action: one concrete fix or verification step.
Keep strengths short. The user asked for readiness, so the useful answer is the
remaining risk and the next action.
Example
User:
is this ready to ship?
Response:
Production audit: 68/100, risky, because Stripe webhooks are verified but not idempotent and there is no rollback note for the pending migration.
Blockers:
- Add idempotency for `checkout.session.completed` before fulfilling orders.
- Write and test the rollback path for `20260511_add_billing_state.sql`.
High-value fixes:
- Add a health check that verifies database and payment-provider reachability.
- Add one E2E path for upgrade, webhook fulfillment, and billing-page refresh.
Evidence checked:
- `api/stripe/webhook.ts`
- `db/migrations/20260511_add_billing_state.sql`
- GitHub Actions run for the release branch
Next action: Want me to patch webhook idempotency first?
Anti-Patterns
- Running
npx <package>@latest or a remote scanner as the default audit path.
- Uploading source, secrets, customer data, or private topology to an external
audit service without explicit approval.
- Producing a score without naming the evidence checked.
- Treating green CI as production readiness.
- Ending with a generic "let me know what you want to do."
See Also
- Skill:
security-review
- Skill:
deployment-patterns
- Skill:
e2e-testing
- Skill:
tdd-workflow
- Skill:
verification-loop
1---2name: production-audit3description: Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.4metadata:5 source: https://skillmd.com/skills/mhassan0000/production-audit6 origin: community7---89# Production Audit1011Use this skill when the user asks whether an application is ready to ship, what12could break in production, or what must be fixed before a launch. This is a13maintainer-safe rewrite of the stale community production-audit idea: it keeps14the useful production-readiness lens and removes unpinned external execution and15third-party data sharing.1617## When to Use1819- The user asks "is this production-ready", "what would break in prod", "what20 did we miss", "audit this repo", or "ready to ship?"21- A feature was merged and needs a pre-deploy or post-merge risk pass.22- A public launch, demo, customer rollout, or investor walkthrough is close.23- CI is green but the user wants production risk, not only test status.24- A deployed URL, release branch, PR, or current checkout is available for25 evidence gathering.2627## When Not to Use2829- During active implementation when the right lens is line-level secure coding;30 use `security-review` first.31- For pure libraries, templates, docs-only repos, or scaffolds unless the user32 wants packaging/release readiness rather than application readiness.33- When the user asks for a formal compliance audit. This skill is engineering34 triage, not legal, financial, medical, or regulatory certification.35- When the only available evidence is a product idea with no repo, deployment,36 CI, or runtime surface.3738## How It Works3940Build the audit from local and user-authorized evidence. Do not run unpinned41remote code, upload repository contents to third-party services, or call42external scanners unless the user explicitly approves that specific tool and43data flow.4445Use this order:46471. Establish the release surface.482. Read recent changes and current branch state.493. Inspect runtime, auth, data, payment, background-job, AI, and deployment50 boundaries that actually exist in the repo.514. Check CI, tests, migrations, environment documentation, and rollback path.525. Produce a short ship/block recommendation with specific fixes.5354## Evidence Checklist5556Start with cheap, local signals:5758```text59git status --short --branch60git log --oneline --decorate -2061git diff --stat origin/main...HEAD62```6364Then inspect the project-specific surface:6566- Package scripts, CI workflows, release scripts, Docker files, and deployment67 manifests.68- API routes, webhooks, auth middleware, background workers, cron jobs, and69 database migrations.70- Environment variable documentation and startup checks.71- Observability hooks, error reporting, logs, health checks, and dashboards.72- Rollback, seed, migration, and backfill instructions.73- E2E coverage for the user paths that matter most.7475If a deployed URL is in scope, use browser or HTTP checks only against that URL76and avoid credentialed actions unless the user supplies a safe test account.7778## Risk Lenses7980### Security And Auth8182- Are public routes, API routes, and admin routes clearly separated?83- Are auth and authorization enforced server-side?84- Are secrets kept out of client bundles, logs, example output, and checked-in85 files?86- Are rate limits, CSRF protections, CORS policy, and upload validation present87 where the app needs them?88- Does the AI or agent surface defend against prompt injection, tool abuse, and89 untrusted content crossing into privileged actions?9091### Data Integrity9293- Do migrations run forward cleanly and have a rollback or recovery plan?94- Are destructive migrations, backfills, and data imports staged safely?95- Do database policies, grants, and service-role boundaries match the app's96 tenancy model?97- Are retries idempotent for writes, jobs, and webhook handlers?9899### Payments And Webhooks100101- Are webhook signatures verified before parsing trusted payload fields?102- Is each payment, subscription, or fulfillment webhook idempotent?103- Are replay, duplicate delivery, and out-of-order delivery handled?104- Are test-mode and live-mode credentials separated?105106### Operations107108- Can the app start from a clean checkout using documented commands?109- Are required environment variables named, validated, and fail-fast?110- Is there a health check that proves dependencies are reachable?111- Are deploy, rollback, and incident-owner paths documented?112- Are logs useful without leaking secrets or personal data?113114### User Experience115116- Are the launch-critical paths covered on desktop and mobile?117- Are forms usable on mobile without input zoom, layout overlap, or blocked118 submission states?119- Do loading, empty, error, and permission-denied states tell the user what120 happened?121- Is there a support or recovery path when a critical operation fails?122123## Scoring124125Use scores to force prioritization, not to imply mathematical certainty.126127| Band | Score | Meaning |128| --- | --- | --- |129| Blocked | 0-49 | Do not ship until the top risks are fixed |130| Risky | 50-69 | Ship only behind a small rollout or internal beta |131| Launchable With Caveats | 70-84 | Ship if owners accept the listed risks |132| Strong | 85-100 | No obvious launch blockers from available evidence |133134Cap the score at `69` if any of these are true:135136- Authentication or authorization is missing on sensitive data.137- Payment or fulfillment webhooks are not idempotent.138- Required migrations cannot be run safely.139- Secrets are exposed in client bundles, logs, or committed files.140- There is no rollback path for a high-impact release.141142Cap the score at `84` if CI is not green or the launch-critical path was not143tested end to end.144145## Output Format146147Lead with one sentence:148149```text150Production audit: 76/100, launchable with caveats, with webhook idempotency and rollback docs as the two risks to fix before public launch.151```152153Then list:154155- `Blockers`: must-fix items before deploy.156- `High-value fixes`: next fixes if the user wants to improve the score.157- `Evidence checked`: files, commands, CI, deployed URL, or PRs inspected.158- `Evidence missing`: what would change confidence if provided.159- `Next action`: one concrete fix or verification step.160161Keep strengths short. The user asked for readiness, so the useful answer is the162remaining risk and the next action.163164## Example165166User:167168```text169is this ready to ship?170```171172Response:173174```text175Production audit: 68/100, risky, because Stripe webhooks are verified but not idempotent and there is no rollback note for the pending migration.176177Blockers:178- Add idempotency for `checkout.session.completed` before fulfilling orders.179- Write and test the rollback path for `20260511_add_billing_state.sql`.180181High-value fixes:182- Add a health check that verifies database and payment-provider reachability.183- Add one E2E path for upgrade, webhook fulfillment, and billing-page refresh.184185Evidence checked:186- `api/stripe/webhook.ts`187- `db/migrations/20260511_add_billing_state.sql`188- GitHub Actions run for the release branch189190Next action: Want me to patch webhook idempotency first?191```192193## Anti-Patterns194195- Running `npx <package>@latest` or a remote scanner as the default audit path.196- Uploading source, secrets, customer data, or private topology to an external197 audit service without explicit approval.198- Producing a score without naming the evidence checked.199- Treating green CI as production readiness.200- Ending with a generic "let me know what you want to do."201202## See Also203204- Skill: `security-review`205- Skill: `deployment-patterns`206- Skill: `e2e-testing`207- Skill: `tdd-workflow`208- Skill: `verification-loop`