production-audit

原文涵盖的主题

• Production Audit
• When to Use
• When Not to Use
• How It Works
• Evidence Checklist
• Risk Lenses
• Security And Auth
• Data Integrity

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. 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. 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 evi

这里只展示节选，请以完整原文和当前要求为准。