review-mr

Analyze merge request diffs against main and produce structured review reports.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/thbraet/claude-template --skill review-mr-thbraet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-mr
Source: https://github.com/thbraet/claude-template/tree/main/skills/review-mr
Command: npx skills add https://github.com/thbraet/claude-template --skill review-mr-thbraet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews merge requests by providing a structured report of findings, severity levels, and a clear verdict, reducing review time and risk.

Core Features & Use Cases

  • Independent code review of MR against main for correctness, data science rigor, security, compliance, and convention adherence.
  • Generates a structured findings report with actionable items and a clear merge verdict.
  • Use Case: Before merging, review a feature MR to detect data handling issues, security risks, and governance gaps.

Quick Start

Ask the AI to generate a structured code review report for the current branch diff 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 generate a structured code review report for a branch diff against main?

To generate a structured code review report, analyze the branch diff against main to evaluate correctness, security, and convention adherence. The review produces actionable findings with severity levels and a clear merge verdict to accelerate decision-making.

What is the best way to review a merge request for data science rigor and security risks?

Reviewing a merge request for data science rigor and security risks involves analyzing the code diff for data handling issues, security vulnerabilities, and governance gaps. This process ensures reproducible checks and delivers a clear, actionable report.

Can I use an automated merge request review for compliance and convention adherence?

Yes, automated merge request review can evaluate compliance and convention adherence by analyzing the diff against main. It targets software project workflows to ensure code quality standards are met before generating a final merge verdict.

How do merge request reviews determine severity levels and a final merge verdict?

Merge request reviews determine severity levels and a merge verdict by analyzing the branch diff against main for correctness, security, and governance gaps. The structured findings report categorizes issues by severity to guide the final merge decision.

When do I need a structured review report before merging a feature branch?

You need a structured review report before merging a feature branch to detect data handling issues, security risks, and governance gaps. It provides a clear merge verdict that reduces review time and minimizes the risk of introducing errors.