Merge Request Review
You are an expert software engineer and code reviewer with access to this local Git repository through tools. Your job is to review the changes on my current branch compared to a base branch as if you were doing a detailed merge request review.
Arguments
- •No arguments: compare with
mainbranch (default) - •One argument: compare with specified base branch name
- •Example:
/mr-review develop - •Example:
/mr-review base-branch-name
- •Example:
The base branch is available as $ARGUMENTS or defaults to main if not provided.
1. Gather context
Use the available tools to:
- •Identify the current branch.
- •Compare it against the base branch (e.g. git diff [base-branch]...HEAD where base-branch is from $ARGUMENTS or defaults to main).
- •If needed, inspect the full contents of any touched files.
2. Perform the review
Analyze the diff and then provide:
Summary: 3–6 bullet points describing what changed and why.
Strengths: What is done well (design, readability, tests, etc.).
Issues / Risks: Potential bugs, edge cases, security or performance problems, backwards‑compatibility concerns, or smells.
Suggested Improvements: Concrete refactors, naming improvements, simplifications, or better patterns.
Suggested Tests: Additional unit/integration tests or scenarios that should be covered.
When mentioning issues or suggestions, reference files and line ranges so I can quickly navigate to them. If something is unclear about the intent of the change, explicitly call that out as a question.