mark-mr-ready

Mark a GitLab draft merge request as ready for review.

2|Updated Feb 16, 2026

Search Tags:#automation #developer tools #ci/cd #slack #jira #gitlab #merge request

One-click install

npx skills add https://github.com/dmzoneill/skills --skill mark-mr-ready

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of preparing a draft Merge Request (MR) for review, streamlining the development workflow.

Core Features & Use Cases

Draft Removal: Changes a draft MR to a regular MR, signaling it's ready for feedback.
Automated Checks: Optionally runs linting and documentation checks to ensure code quality before review.
Status Updates: Updates Jira tickets to "In Review" and posts notifications to Slack.
Use Case: When you've finished coding a feature and want to get feedback from your team, use this skill to automatically transition your MR to a reviewable state, ensuring all checks pass and relevant parties are notified.

Quick Start

Use the mark-mr-ready skill to mark merge request 123 as ready for review.

Frequently Asked Questions about mark-mr-ready

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

FAQPage Schema

How do I mark a draft merge request as ready for review in GitLab?▼

To mark a draft merge request as ready for review in GitLab, you must remove its draft status. This skill automates that process by transitioning the MR to a reviewable state and optionally running code quality checks.

Can I automatically update Jira ticket status when a GitLab MR is ready for review?▼

Yes, you can automatically update Jira ticket status when a GitLab MR is ready for review. This skill transitions associated Jira tickets to the 'In Review' status upon removing the draft designation.

What is the best way to notify Slack when a merge request is ready for review?▼

The best way to notify Slack when a merge request is ready for review is through automated CI/CD workflows. This skill posts notifications directly to designated Slack channels once the MR draft status is successfully removed.

How do I run linting and documentation checks before a merge request review?▼

To run linting and documentation checks before a merge request review, you can use automation tools. This skill optionally executes these checks to ensure code quality standards prior to transitioning the MR for team feedback.

Do I need a specific Jira key to transition a merge request from draft to review?▼

You do not need a specific Jira key to transition a merge request from draft to review, as it is an optional parameter. The skill requires the MR ID and project details to remove the draft status, while Jira integration is optional.