branch-change-reviewer

A branch review evaluates git branch changes against a target branch to identify regressions, architecture issues, and testing gaps. It generates a Markdown report with severity-ranked findings to highlight actionable engineering risks before merging.

You can generate a code review report by comparing your current branch against origin/main. The process produces a concise Markdown artifact containing severity-ranked findings, open questions, and summaries for team engineering workflows.

When analyzing branch changes, you should check for regressions, maintainability concerns, missing tests, architectural drift, and style issues. These engineering risk assessments help identify meaningful problems before changes are merged.

No, the branch review process does not modify your source code. It strictly evaluates branch diffs and surrounding context to produce focused review findings and Markdown artifacts, ensuring your repository remains untouched during the assessment.

The best way to assess architectural drift in a feature branch is through a diff-based review against the target branch. This analysis identifies maintainability concerns and architectural issues, generating actionable findings for your team.