Agent skill
mr-tracker
Tracks and monitors GitLab merge request activity including comments, status, and real-time updates
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/mr-tracker
SKILL.md
Features
- Comment monitoring: Fetches and displays 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
Installation
-
Ensure you have the required dependencies:
bash# GitLab CLI pip install glab # Or follow installation instructions at https://gitlab.com/gitlab-org/cli # jq for JSON processing (usually pre-installed on most systems) # On macOS: brew install jq # On Ubuntu: sudo apt-get install jq -
Make sure the script is executable:
bashchmod +x scripts/mr_tracker.sh
Usage
Show comments for a specific MR:
./scripts/mr_tracker.sh comments 123
Show limited comments:
./scripts/mr_tracker.sh comments 123 5 # Show only 5 most recent comments
Show MRs for current branch:
./scripts/mr_tracker.sh current
Watch MR for new comments:
./scripts/mr_tracker.sh watch 123 30 # Check every 30 seconds
Show MR status and summary:
./scripts/mr_tracker.sh status 123
Show help:
./scripts/mr_tracker.sh help
Command Reference
comments <mr_iid> [limit]
Displays comments for a specific merge request with rich context including:
- Author information with username
- Creation date
- File path and line numbers for diff comments
- Comment body with truncation for long comments
current
Lists all merge requests for your current git branch, showing:
- MR number and title
- Current state (opened, closed, merged)
watch <mr_iid> [interval]
Monitors an MR for new comments in real-time:
- Shows initial comment count
- Checks for new comments at specified intervals (default: 60 seconds)
- Displays only new comments when detected
- Continues until interrupted with Ctrl+C
status <mr_iid>
Shows comprehensive MR information:
- Title and state
- Author and branch information
- Creation and update timestamps
- Approval count and merge status
- File changes summary
- Recent comments
Configuration
GitLab Project
The MR tracker assumes the project path cnty-ai/continuity. To change this, modify the project path in scripts/mr_tracker.sh:
# Change this line in multiple places:
projects/cnty-ai%2Fcontinuity/merge_requests/
# To your project:
projects/your-group%2Fyour-project/merge_requests/
Customizing Output
The script uses jq for JSON processing and formatting. You can modify the jq queries in the script to customize the output format.
Examples
Example 1: Monitor MR activity
# Watch MR #123 for new comments every 30 seconds
./scripts/mr_tracker.sh watch 123 30
Output:
👀 Watching MR #123 for new comments (checking every 30s)...
Press Ctrl+C to stop
📊 Initial comment count: 3
🆕 New comments detected! (Mon Oct 19 10:30:15 EDT 2025)
================================
🔍 DIFF COMMENT
👤 John Doe (@johndoe) - 2025-10-19
📁 File: src/components/Button.tsx
📍 Line: 45→47
Consider adding error handling for the edge case here...
─────────────────────────────────────────────────
Example 2: Check current branch MRs
./scripts/mr_tracker.sh current
Output:
🔍 Looking for MRs on branch: feature/new-button
==========================================
MR #456: Add new button component (State: opened)
Example 3: Get MR status
./scripts/mr_tracker.sh status 456
Output:
📊 MR #456 Status
==================
Title: Add new button component
State: opened
Author: Jane Smith
Source Branch: feature/new-button
Target Branch: main
Created: 2025-10-19T09:15:30.000Z
Updated: 2025-10-19T10:30:15.000Z
👍 Approvals: 2
🔁 Merge Status: can_be_merged
📝 Changes: 3 files, +45 -12
📝 Recent Comments:
📝 Comments for MR #456 (with file/line context):
==================================================
💬 GENERAL COMMENT
👤 John Doe (@johndoe) - 2025-10-19
Looks good! Just one suggestion...
──────────────────────────────────────────────────
Troubleshooting
Common Issues
-
"glab command not found"
- Install GitLab CLI: https://gitlab.com/gitlab-org/cli
- Authenticate:
glab auth login
-
"jq command not found"
- Install jq:
brew install jq(macOS) orsudo apt-get install jq(Ubuntu)
- Install jq:
-
"Not in a git repository"
- Make sure you're in a git repository when using
currentcommand
- Make sure you're in a git repository when using
-
"No MRs found for branch"
- Check that you're on the correct branch
- Verify the MR exists and targets the correct project
-
"MR #X not found"
- Verify the MR number is correct
- Check that the MR exists in the configured project
Debug Mode
For debugging API calls, you can run glab commands directly:
glab api "projects/cnty-ai%2Fcontinuity/merge_requests/123"
Contributing
To extend this tool:
- Add new commands: Extend the case statement in the main script logic
- Customize output format: Modify the
jqqueries for different formatting - Add new project support: Update the project path configuration
- Enhance monitoring: Add additional real-time features like status changes
License
This skill is part of the OpenCode project and follows the same license terms.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?