code-review

Code reviews systematically examine submitted code for bugs, performance issues, and adherence to standards before approval. Structure your review by checking for common code smells, verifying logic correctness, assessing performance impact, and ensuring style compliance—then provide clear, actionable feedback that educates rather than criticizes.

Focus on identifying logic errors, edge cases, and potential runtime failures. Check for code smells like duplicate logic or unclear naming, verify adherence to coding standards, assess maintainability, and confirm the changes don't introduce security or performance regressions before approval.

Constructive feedback is clear, specific, and educational. Explain *why* a change matters, suggest concrete improvements with examples, acknowledge good work, and frame suggestions as questions or learning opportunities rather than directives to make feedback collaborative and actionable.

Verification ensures changes work as intended and don't break existing functionality. Testing and understanding the impact before approval prevents bugs from reaching production, maintains code quality, and confirms the implementation actually solves the stated problem.

Yes. Code reviews enforce consistency by catching deviations from standards, best practices, and team conventions during the review gate. Structured feedback on style, patterns, and architectural decisions ensures the codebase remains maintainable and aligned across the team.

Address disagreements by discussing the trade-offs, referencing team standards or architectural decisions, and focusing on the code's impact rather than personal preference. When consensus isn't obvious, escalate thoughtfully or document the decision to maintain forward momentum.