emon5122

Critically review code for bugs, quality issues, security vulnerabilities, performance problems, architecture concerns, and testing gaps. Use when: asked to review/fix code, find bugs, suggest improvements, audit quality, check security, recommend refactoring, or verify changes before commit.

Iteratively review and fix code until the code-critic is satisfied. Use when: asked to fix code until clean, polish changes, self-heal code, iterate on review feedback, keep fixing until no issues remain, or run the critic in a loop.