fight-club

Use when reviewing code for structural quality — factoring, coupling, cohesion, abstraction levels, information hiding, and simplicity. Adversarial: challenges every design decision, not just obvious violations.

Use when reviewing code for security — authentication, authorization, input validation, injection, data exposure, cryptography, or trust boundaries. Adversarial: assumes the attacker has read your code and is actively looking for a way in.

Use when reviewing code for performance — database queries, network calls, collection processing, caching, concurrency, or code on hot paths. Adversarial: finds the scaling assumptions that will collapse under real load.

Use when reviewing tests or test coverage — unit tests, integration tests, test suites, or PRs that include tests. Adversarial: finds the bugs the tests would miss, not just the tests that are missing.

Use when reviewing code or designs for production reliability — failure modes, operational risk, silent failures, recovery difficulty, and incident scenarios. Adversarial: imagines the worst production incident this code could cause and works backwards.