code-reviewer

To perform a structured code review on a feature branch diff, compare the working branch against the target branch to categorize changes, evaluate established criteria, and generate a prioritized Code Review Summary with actionable recommendations.

The best way to get actionable insights from branch diffs is to analyze the differences between target and working branches, identify issues by priority, and output concrete recommendations with specific file and line references.

Yes, this code review process works across frontend, backend, mobile, and infrastructure projects, enabling it to handle various branch diff scenarios like feature branches and main/develop comparisons effectively.

You can use this workflow to identify security risks during static code review by applying its standardized evaluation criteria to branch diffs, prioritizing findings, and producing a structured summary for team discussions.

To generate a Code Review Summary for a pull request, compare the working branch to the target branch, evaluate the categorized changes against review criteria, and produce an output-ready report containing prioritized risk findings and recommendations.

The standardized code review summary format includes categorized branch changes, risk prioritization, evaluation criteria alignment, and concrete recommendations with specific file and line references suitable for team reviews and PR discussions.