code-reviewer

Perform a code review focused on maintainability and design clarity by analyzing diffs to document evidence-based risks, propose minimal fixes with concrete locations, and outline validation steps including residual risk considerations.

The best way to identify risky implementation choices in a code change is by assessing cyclomatic complexity, API clarity issues, and unclear ownership to propose high-impact fixes with concrete rationale and validation steps.

Assess maintainability risks like cyclomatic complexity and duplication in a diff by analyzing the affected file paths to surface evidence-based findings and recommend minimal, actionable fixes for long-term quality.

Code review software should provide regression considerations for long-term impact by specifying clear validation steps and residual risks alongside actionable fixes for downstream integration and future evolution.

You can use diff-analysis for code reviews across multiple projects by supplying the change diff or affected file paths to surface critical maintainability risks, readability issues, and recommended actions regardless of project boundaries.

You should not use automated diff-analysis when the primary goal is verifying mere functionality rather than addressing long-term code quality, readability, design clarity, and downstream impact through evidence-based findings.