Review code against the MiKode coding philosophy. Use after implementation or refactoring to identify correctness issues, architectural coupling, unnecessary complexity, weak tests, avoidable technical debt, scope creep, and generated-code patterns. When architecture or security is the primary concern, delegate its deeper review to mikode-architecture-review or mikode-security-review when available. Produce prioritized, actionable findings without inventing problems merely to provide feedback.
