platform.gitlab.gitlab-mr-review-workflow

Use for GitLab merge request review runs triggered by @Nine1bot comments or merge request webhooks.

6 stars

Best use case

platform.gitlab.gitlab-mr-review-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use for GitLab merge request review runs triggered by @Nine1bot comments or merge request webhooks.

Teams using platform.gitlab.gitlab-mr-review-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/gitlab-mr-review-workflow/SKILL.md --create-dirs "https://raw.githubusercontent.com/contrueCT/nine1bot/main/packages/platform-gitlab/skills/review/gitlab-mr-review-workflow/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/gitlab-mr-review-workflow/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How platform.gitlab.gitlab-mr-review-workflow Compares

Feature / Agent	platform.gitlab.gitlab-mr-review-workflow	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Use for GitLab merge request review runs triggered by @Nine1bot comments or merge request webhooks.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

Best AI Skills for Claude

Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.

Cursor vs Codex for AI Workflows

Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.

SKILL.md Source

# GitLab MR Review Workflow

Treat the GitLab merge request as the source of truth for scope. Review only the included diff manifest and provided repository context.

This is a read-only review workflow by default. Do not edit files, run fix scripts, or turn the review into a general implementation task unless the PM input explicitly sets `fixMode=true`.

Stage order:

1. discovery: identify changed files, risk areas, evidence, assumptions, and blocked conditions.
2. spec: decide whether available requirements, design notes, and task context are enough to review safely.
3. implementation: dispatch focused custom subagents when architecture, frontend, backend, QA, or security review is needed.
4. verification: merge structured findings and ask PM to decide severity, conflicts, and release risk.
5. fix: only propose or apply minimal patches when the run explicitly allows code changes.
6. closed: render a concise GitLab summary and include skipped files, fallback inline comments, and timed-out agents.

Never invent findings outside the diff. If the diff is blocked, truncated, or empty after filters, stop and report the blocked state.

The PM coordinator must finish with one fenced JSON block tagged `GITLAB_REVIEW_RESULT`. The JSON must match the ReviewStageResult schema from `platform.gitlab.review-finding-schema`.