platform-gitlab-gitlab-mr-review-workflow

스타8

포크2

업데이트2026년 5월 10일 04:42

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

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

contrueCT

contrueCT/nine1bot

GitHub 저장소 열기 Creator 저장소 보기

다운로드

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:

discovery: identify changed files, risk areas, evidence, assumptions, and blocked conditions.
spec: decide whether available requirements, design notes, and task context are enough to review safely.
implementation: dispatch focused custom subagents when architecture, frontend, backend, QA, or security review is needed.
verification: merge structured findings and ask PM to decide severity, conflicts, and release risk.
fix: only propose or apply minimal patches when the run explicitly allows code changes.
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.

이 저장소의 다른 Skills

같은 저장소

platform-gitlab-gitlab-comment-rendering

contrueCT/nine1bot

Use to render GitLab review results into concise merge request or commit comments.

2026-05-108

platform-gitlab-gitlab-commit-review-workflow

contrueCT/nine1bot

Use for narrow GitLab commit review runs triggered from commit comments.

2026-05-108

platform-gitlab-pm-risk-routing

contrueCT/nine1bot

Use to choose which custom subagents should be created for a GitLab review run.

2026-05-108

platform-gitlab-review-finding-schema

contrueCT/nine1bot

Use to produce structured GitLab code review findings and the final GitLab review result.

2026-05-108

platform-gitlab-security-review-policy

contrueCT/nine1bot

Use for security review of GitLab MR or commit diffs.

2026-05-108

platform-gitlab-spec-gate-review

contrueCT/nine1bot

Use to decide whether a GitLab review has enough product and technical context to proceed.

2026-05-108

name	platform.gitlab.gitlab-mr-review-workflow
description	Use for GitLab merge request review runs triggered by @Nine1bot comments or merge request webhooks.

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:

discovery: identify changed files, risk areas, evidence, assumptions, and blocked conditions.
spec: decide whether available requirements, design notes, and task context are enough to review safely.
implementation: dispatch focused custom subagents when architecture, frontend, backend, QA, or security review is needed.
verification: merge structured findings and ask PM to decide severity, conflicts, and release risk.
fix: only propose or apply minimal patches when the run explicitly allows code changes.
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.