Address MR Review Comments

VerifiedCaution

Handle MR review threads one by one with progress tracking and fix/reply/defer/skip actions.

Sby Skills Guide Bot
DevelopmentIntermediate
4010/19/2026
Claude Code
#code-review#merge-request#gitlab#glab#review-workflow

Recommended for

Our review

Works through GitLab merge request review threads one at a time with minimal per-thread guidance, tracking progress in a dedicated file.

Strengths

  • Handles each discussion thread in isolation, showing only the author, file/line and comment text so the context stays focused.
  • Offers five explicit actions (fix, reply, defer, skip, done) rather than leaving the agent to improvise.
  • Keeps a `.specwork/_review/<id>-mr-address.md` progress file that is reused on later runs to skip threads already handled.
  • Falls back to a manual paste mode when `glab` is unavailable, accepting one comment at a time with `---` or `done` to control the flow.

Limitations

  • Assumes you are on the branch tied to an open MR and relies on `glab` for automatic detection.
  • Reads only the file or lines needed for the current thread, so multi-file fixes depend on what the agent chooses to open.
  • In manual mode replies are printed for pasting rather than posted automatically.
When to use it

Reach for it when an open MR has a backlog of review comments you want to resolve methodically without losing track.

When not to use it

Skip it when you want an internal code review before the MR exists, or when no review tooling and no pasted comments are available.

Security analysis

Caution
Quality score85/100

The skill uses powerful tools (git push, glab, python3) for a legitimate code review workflow. No destructive, exfiltrating, or obfuscated actions are instructed. The risk is limited to accidental remote changes or unintended commit/push, which is inherent to the task.

Findings
  • •Allows `git push` which modifies remote repositories
  • •Allows unrestricted `glab:*` commands that can alter GitLab issues/MRs
  • •Allows arbitrary `python3:*` execution

Examples

Address open MR comments
Go through the unresolved review threads on my current MR and help me fix them one by one.
Manual paste mode
glab isn't installed here — let me paste the review comments one at a time and you handle each of them.
Resume where we left off
Continue addressing the MR review threads, skipping the ones already recorded in the progress file.

name: mr-address description: Work through open MR review comments with minimal per-thread guidance allowed-tools: Read, Edit, Write, Bash(git status:), Bash(git diff:), Bash(git add:), Bash(git commit:), Bash(git push:), Bash(git rev-parse:), Bash(git branch:), Bash(glab:), Bash(find .:), Bash(grep -r:), Bash(cat .specwork/_review/), Bash(python3:), Bash(command -v:*)

Address MR Review

Load: view ${CLAUDE_PLUGIN_ROOT}/skills/mr-address/SKILL.md


Description

Handle MR review threads one by one and track progress in .specwork/_review/<id>-mr-address.md.

Use glab if available; otherwise switch to manual paste mode. Keep prompts short and only show the current thread.


Flow

  1. Detect glab, branch, and MR
  2. Load unresolved threads or manual comments
  3. Skip already-handled items from the progress file
  4. Handle threads one at a time
  5. Update progress, then offer commit/push

Manual Mode

Ask for one pasted comment at a time. Use --- to confirm or done to stop. Parse optional file: and line: hints. Use manual-N ids in the progress file.


Thread Actions

Show only:

  • author
  • file/line if available
  • comment text
  • fix / reply / defer / skip / done

Actions:

  • fix: make the change, show a minimal diff summary, confirm, resolve
  • reply: capture the reply text, confirm, post or print it for manual paste
  • defer: mark pending in the progress file
  • skip: move on without recording
  • done: stop the session

Read only the file or lines needed for the current thread.


Progress File

Update .specwork/_review/<id>-mr-address.md after each handled thread.

# Address MR Review: <id>

MR: !<iid>

## Addressed
- [x] <discussion-id>: @author — fixed
- [x] <discussion-id>: @author — replied

## Deferred
- [ ] <discussion-id>: @author

Reuse this file on later runs to skip handled threads.


End of Session

Session complete
  ✓ fixed: 3
  ✓ replied: 1
  ○ deferred: 1
  – skipped: 2

If files changed, offer one commit and an optional push.


Requirements

  • Run from the branch tied to the MR
  • An open MR must exist
  • glab is optional; manual mode is allowed

Related Skills

  • mr — creates the MR this skill reads from
  • commit — commit addressed review changes
  • code-review — internal review before the MR is open
Related skills