Verified:Website 𝕏@ProchazkaFilip GitHub

post

Posts an existing code-review report to a GitLab merge request as inline diff comments and a summary comment.

15|1|Updated Jan 3, 2026

Search Tags:#code review #gitlab #merge request #glab #review report #migration safety #diff comments

One-click install

npx skills add https://github.com/fprochazka/claude-code-plugins --skill post-fprochazka

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: post
Source: https://github.com/fprochazka/claude-code-plugins/tree/main/plugins/code-review/skills/post
Command: npx skills add https://github.com/fprochazka/claude-code-plugins --skill post-fprochazka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running a multi-agent code review, manually copying findings into GitLab MR comments is tedious and error-prone. This Skill publishes the review report already produced in the session to the merge request, placing each finding exactly where it belongs. ## Core Features & Use Cases - Inline diff comments: Anchors each finding to the correct file and line in the MR diff using glab-discussion, with severity labels, mermaid diagrams, and suggested fixes. - Migration safety threads: Posts each database migration assessment as its own thread with verdict, lock behavior, size estimates, and replication impact. - Summary comment: Publishes one MR-level comment with the verdict, cross-cutting findings, coverage, and unresolved discussions. - Use Case: After running /code-review:full on a branch, invoke this Skill to publish all findings to the GitLab MR so reviewers and approvers can discuss them in threads. ## Quick Start Ask the assistant to post the code-review report from this session to the current GitLab merge request.

Frequently Asked Questions about post

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

FAQPage Schema

How do I post code review findings to a GitLab merge request?▼

Run /code-review:full first to generate the report in the session, then invoke this Skill. It anchors each finding to the correct diff line via glab-discussion and adds one summary comment with the overall verdict.

How to add inline diff comments on GitLab MR with glab?▼

The Skill fetches per-file diff info with glab-discussion diff to get base/head SHAs and line refs, then posts each finding with glab-discussion write as an anchored diff note, one finding per thread.

Can I post a review without running the full code review first?▼

No. The Skill only posts an existing report from the current session and never re-runs the review or re-derives findings. If no report exists, it stops and tells you to run /code-review:full first.

What happens if a finding's line is not in the MR diff?▼

The finding is moved from the inline bucket to the summary comment instead of being posted on an unchanged line. Migration safety entries anchor on the statement's new first line, or are dropped with a notice if the file left the diff.

Why are mermaid diagrams limited in posted review comments?▼

GitLab auto-renders only 2000 characters of mermaid per page, shared across the page. The Skill caps posted comments at three diagram fences, prioritizing Blocking findings, and reports any fences it dropped.