check-mr-feedback

Scan GitLab merge requests for human-authored comments requiring attention or suggesting meetings.

2|Updated Feb 16, 2026

Search Tags:#developer tools #code review #feedback #collaboration #gitlab #merge request

One-click install

npx skills add https://github.com/dmzoneill/skills --skill check-mr-feedback

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: check-mr-feedback
Source: https://github.com/dmzoneill/skills/tree/main/check-mr-feedback
Command: npx skills add https://github.com/dmzoneill/skills --skill check-mr-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify and act on feedback left on their Merge Requests (MRs), ensuring timely responses and efficient code review cycles.

Core Features & Use Cases

Filter Bot Comments: Automatically excludes comments made by bots, focusing on human feedback.
Identify Actionable Items: Detects comments that require a response, such as questions or requests for changes.
Meeting Request Detection: Flags comments that suggest a meeting or discussion.
Use Case: Before starting your day, run this Skill to see all open MRs that have new comments needing your attention, or to identify any requests for meetings that need scheduling.

Quick Start

Check my open merge requests for any feedback that requires a response.

Frequently Asked Questions about check-mr-feedback

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

FAQPage Schema

How do I check my GitLab merge requests for reviewer comments?▼

Scanning open merge requests for reviewer comments automatically filters out bot activity and surfaces human-authored feedback. This process identifies actionable code review input and flags comments suggesting meetings to ensure timely developer responses.

Can I filter merge request feedback to exclude bot comments?▼

Yes, filtering merge request feedback to exclude bot comments is supported. The tool automatically removes automated bot activity, allowing you to focus exclusively on actionable human feedback left by your reviewers on GitLab merge requests.

How do I identify meeting requests in GitLab merge request comments?▼

Identifying meeting requests in GitLab merge request comments involves scanning open MRs and detecting language suggesting a discussion. The tool flags these specific reviewer comments so you can schedule meetings and facilitate efficient developer workflows.

How do I find comments on a specific GitLab merge request ID?▼

Finding comments on a specific GitLab merge request ID is supported through specific MR ID filtering. This narrows the code review feedback scan to a single merge request, isolating its actionable reviewer comments and meeting requests.

What is the best way to track actionable feedback on open merge requests?▼

The best way to track actionable feedback on open merge requests is to use an automated scanning tool that detects questions and change requests. This approach highlights necessary responses and bot-filtered feedback to facilitate efficient developer workflows.