mr-tracker

Track GitLab merge request comments, status, and real-time updates.

Updated Jul 8, 2024

Search Tags:#automation #monitoring #real-time #diff #gitlab #merge-request

One-click install

npx skills add https://github.com/alexismanuel/dotfiles --skill mr-tracker

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mr-tracker
Source: https://github.com/alexismanuel/dotfiles/tree/main/.opencode/skill/mr-tracker
Command: npx skills add https://github.com/alexismanuel/dotfiles --skill mr-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glab, jq, git, and includes scripts (resource) components.

What problem does it solve?

This Skill helps software teams monitor GitLab merge requests in real-time, surfacing new comments, status changes, and diffs to reduce MR review latency and context-switching.

Core Features & Use Cases

Comment monitoring: Fetches MR comments with file/line context
Real-time watching: Watch MRs for new comments with customizable intervals
Status overview: Shows MR status, approvals, and changes summary
Current branch detection: Automatically finds MRs for your current branch
Diff context: Shows file paths and line numbers for diff comments
Interactive monitoring: Live updates with timestamp notifications

Quick Start

Show MR comments: ./scripts/mr_tracker.sh comments <MR_IID>
Show limited comments: ./scripts/mr_tracker.sh comments <MR_IID> 5
Show MRs for current branch: ./scripts/mr_tracker.sh current
Watch MR for new comments: ./scripts/mr_tracker.sh watch <MR_IID> 30
Show MR status: ./scripts/mr_tracker.sh status <MR_IID>

Frequently Asked Questions about mr-tracker

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

FAQPage Schema

How do I monitor GitLab merge request comments in real-time?▼

Real-time MR comment monitoring fetches new comments with file and line context at customizable intervals. Use the watch command with an MR ID and interval in seconds to receive live updates with timestamps, reducing review latency and context-switching.

Can I automatically track merge requests for my current branch?▼

Yes, the current branch detection feature automatically identifies and displays MRs associated with your active branch without requiring manual MR ID lookup, streamlining branch-specific monitoring.

What information does MR status overview provide?▼

MR status overview displays approval state, change summary, and current merge request status in a single view, giving teams immediate visibility into review progress and blockers.

Do I need GitLab CLI installed to track merge requests?▼

Yes, GitLab MR tracking requires glab (GitLab CLI), jq for JSON processing, git, and a configured project path to fetch MR metadata, discussions, and notes from your GitLab instance.

How do I retrieve comments from a specific merge request with context?▼

The comments command fetches all MR discussions with associated file paths and line numbers, optionally limited to a specified count, preserving the code context needed for efficient review.

What's the difference between watching and polling merge requests?▼

Watching MRs continuously checks for new comments at user-defined intervals with formatted notifications, whereas status checks provide a single-point-in-time summary of approvals and changes without continuous monitoring.