skills.rest
zbruhnke
zbruhnkeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review-mr

Analyzes merge requests by comparing branches and summarizing code changes with issue severity categories.

16|3|Updated Jan 9, 2026
Search Tags:#code quality#git#developer tools#code review#pull request#merge request
One-click install
npx skills add https://github.com/zbruhnke/claude-code-starter --skill review-mr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-mr
Source: https://github.com/zbruhnke/claude-code-starter/tree/main/.claude/skills/review-mr
Command: npx skills add https://github.com/zbruhnke/claude-code-starter --skill review-mr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process for merge requests, ensuring thorough analysis and constructive feedback before merging.

Core Features & Use Cases

  • Automated Diff Analysis: Compares branches, summarizes changes, and identifies potential issues.
  • Structured Feedback: Provides actionable insights categorized into critical, important, and minor concerns.
  • Use Case: Before merging a feature branch into main, use this Skill to get a comprehensive review that highlights security risks, potential bugs, and areas for improvement.

Quick Start

Use the review-mr skill to review the current branch against main.

Frequently Asked Questions about review-mr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a merge request and identify code quality issues before merging?▼

To review a merge request, compare the feature branch against main to summarize code changes and highlight concerns. This process categorizes feedback into critical, important, and minor issues with specific file and line references for pre-merge quality assurance.

Can I automate pull request code reviews to catch security risks and bugs?▼

Yes, automated diff analysis evaluates pull request code changes to catch security risks and potential bugs. It compares branches and provides structured, actionable feedback to facilitate thorough developer collaboration before merging.

What is the best way to analyze git branch differences for potential issues?▼

The best way to analyze git branch differences is by running an automated diff comparison that summarizes changes and flags concerns. This highlights critical issues, potential bugs, and areas for improvement using specific file and line references.

Does this code review process provide structured feedback for developers?▼

Yes, the code review process provides structured feedback for developers by categorizing concerns into critical, important, and minor issues. This ensures actionable insights are delivered with specific file and line references for clear communication.

How do I highlight critical issues in a merge request diff?▼

To highlight critical issues in a merge request diff, analyze the branch comparison to identify and categorize concerns. The review isolates critical problems alongside important and minor issues, providing specific file and line references for targeted fixes.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

Git Branches

List and visualize Git branch status with remote tracking and synchronization.

Community
Intermediate
MohibShaikhMohibShaikh
11

commit

Stage changes, create a contextual commit message, and push the current branch.

Community
Intermediate
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate
involvexinvolvex

security

Identify and mitigate security vulnerabilities in Solidity smart contracts.

Community
Advanced