Code Audit

Audit existing code (a whole repo, a directory, a single file, or a pointed-at function/class) along one or more quality dimensions, then either report the findings or safely fix them. Dimensions: clean-code (speaking names, single responsibility), reuse/DRY, simplicity (de-over-engineering), performance/ efficiency, security, and robustness (error handling, edge cases, validation, concurrency). Two modes: a prioritized findings report (default), or a behavior-preserving auto-fix (--fix) that applies safe refactorings and then runs the project's tests/build to prove valid-input behavior is unchanged. Use this whenever the user wants to review, audit, check, harden, clean …