mdlockyer/production-code-audit

Audit a codebase the way years of production use would: find the show-stoppers and the small edge-case bugs, verify each one, then implement approved fixes. Use whenever the user asks for an audit, a review of a whole repo or module, a production-readiness or hardening pass, a bug hunt, a 'what will break' assessment, or says things like 'make this solid', 'find the bugs', 'is this ready to ship', 'what did we miss', or 'review this for issues'. Use it even for a single service or package, and even when the user does not say the word 'audit'. Not for reviewing a single PR diff (use a PR-review workflow for that).