domains / families / software-engineering / production-code-audit
Deep-scan a codebase, understand its architecture and patterns, then produce a comprehensive audit report with prioritized fixes. Optionally apply changes on a feature branch with a PR for review. Covers security, performance, error handling, logging, testing, and documentation. Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations
The two copies overlap heavily in the audit workflow (discovery, line-by-line issue detection, prioritized fixes, verification, and examples), but they disagree on the core operating mode and safety constraints. The sickn33 copy is framed as an autonomous, end-to-end transformation that directly fixes issues and adds infrastructure, and it defers to a separate detailed guide. The LeoYeAI copy explicitly defines a default read-only audit mode, requires fixes to be applied on a dedicated branch with a draft PR, and adds specific constraints for secrets handling and test execution. Crowning one copy would hide the other's real alternative workflow and safety rules, so the correct decision is to combine them and surface the conflicts.