Verified:GitHub

re-review-mr

Re-review GitLab and GitHub MRs by assessing addressed comments and new changes.

Updated Nov 12, 2025

Search Tags:#automation #github #gitlab #pr #code-review #mr #re-review

One-click install

npx skills add https://github.com/f-esquivel/dotfiles --skill re-review-mr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: re-review-mr
Source: https://github.com/f-esquivel/dotfiles/tree/main/claude/skills/re-review-mr
Command: npx skills add https://github.com/f-esquivel/dotfiles --skill re-review-mr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-review MR/PRs by reading review history, assessing addressed comments, and evaluating only new changes since the last round.

Core Features & Use Cases

Bootstraps previous feedback into a structured review context.
Analyzes deltas limited to MR-scoped files and surfaces unresolved issues for new changes.
Generates clear, ready-to-post comments and an auditable review history.

Quick Start

Provide the MR/PR number to start a re-review; Claude will fetch history, compute delta, and prepare inline comments.

Frequently Asked Questions about re-review-mr

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

FAQPage Schema

How do I re-review a pull request after the author has addressed my comments?▼

Re-reviewing a pull request involves reading the review history, checking which comments were resolved, and evaluating only the new code deltas since the last round to generate fresh, ready-to-post inline comments.

What is the best way to continue a code review across different Git platforms?▼

Continuing code reviews across platforms requires a tool that enforces platform detection for GitHub and GitLab, calculates MR-scoped deltas, and drafts new comments according to your project conventions.

Can I automate checking if unresolved issues are fixed in new merge request changes?▼

Yes, you can automate this by bootstrapping previous feedback into a structured context, analyzing MR-scoped file deltas, and surfacing unresolved issues specifically within the new changes since the last review.

How do I generate inline comments for a merge request re-review?▼

You generate inline comments by providing the MR number to fetch history, computing the delta of new changes, and preparing structured comments based on history-driven verdicts and safe posting workflows.

Does automated PR re-review evaluate the entire codebase or just the latest delta?▼

Automated PR re-review evaluates only the latest delta. It limits analysis to MR-scoped files and assesses only the new changes introduced since the last review round to keep feedback scoped and relevant.