review-comment

Drafts human-voiced MR/PR review comments from verified findings and posts them via glab or gh.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/bearded-giant/claude-code-config --skill review-comment-bearded-giant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-comment
Source: https://github.com/bearded-giant/claude-code-config/tree/main/skills/review-comment
Command: npx skills add https://github.com/bearded-giant/claude-code-config --skill review-comment-bearded-giant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning raw code review findings into a comment that reads like a human reviewer wrote it is tedious, and pasting severity tags, triage tables, and citation chains into an MR makes authors tune out. This Skill rewrites verified findings into concise prose, shows the draft for approval, and posts it to GitLab or GitHub. ## Core Features & Use Cases - Human-voiced rewriting: Strips scaffolding (severity labels, tables, verdict matrices) and leads each finding with user impact, one citation per claim, and a closing note on what is right. - Approval gate: Shows the drafted comment in chat and waits for approval before posting, unless the user passes --post up front. - Multi-platform posting: Posts via glab for GitLab, gh for GitHub, or a curl fallback against the GitLab API when glab is not authenticated, with optional line-anchored inline threads. - Use Case: After running an adversarial review on a merge request, say "post this as a review comment" to get a polished blocker-focused comment drafted, approved, and published with its note URL reported back. ## Quick Start Ask the assistant to post the current review findings as a comment on your merge request, for example by saying "post this as a review comment on MR 42".

Frequently Asked Questions about review-comment

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

FAQPage Schema
How do I post code review findings as an MR comment?

Run a review skill first so findings exist in session, then invoke /review-comment or say "post this as a review comment". The Skill drafts a human-voiced comment, shows it for approval, and posts it via glab or gh.

How do I comment on a GitLab merge request from the command line?

Use glab mr note create with the MR IID and project path, passing the comment body from a file. If glab is not authenticated for that host, fall back to curl against the GitLab notes API with a PRIVATE-TOKEN header.

Does this work with GitHub pull requests as well as GitLab?

Yes. GitHub pull requests are posted with gh pr comment using a body file, while GitLab merge requests use glab mr note create or the curl API fallback. The drafting and approval steps are identical for both.

Can I skip the approval step and post the review comment directly?

Yes. Pass --post or say "post it" up front and the Skill skips the draft preview and posts immediately. Without that flag it always shows the fenced draft in chat and waits for your approval.

When should I use inline review comments instead of one summary comment?

Use line-anchored inline threads only when a finding sits on a line the latest diff actually touches. Findings in untouched files must go in the main note, and one review should not be split across many inline threads.

Why does the review comment drop severity labels and tables?

Severity tags, verdict matrices, and citation chains are scaffolding from the review process, not something an MR author needs. The Skill rewrites findings as prose that leads with user impact, which reads like a real reviewer and keeps credibility.