watch

Reviews a branch's merge request and watches it until every finding is addressed or refuted.

15|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/fprochazka/claude-code-plugins --skill watch-fprochazka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: watch
Source: https://github.com/fprochazka/claude-code-plugins/tree/main/plugins/code-review/skills/watch
Command: npx skills add https://github.com/fprochazka/claude-code-plugins --skill watch-fprochazka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a merge request is rarely a one-shot event: findings get posted, the author pushes fixes, threads need revisiting, and someone must track which blockers are still open. This Skill automates the reviewer side of that loop on GitLab, keeping the review alive until every blocking finding and suggestion is settled. ## Core Features & Use Cases - Full MR review and posting: Runs a complete code review of the current branch's merge request against the remote refs, posts inline and summary comments, and hands the work back to the author per the review-handshake convention. - Continuous watching via the glab:mr-watch agent: Spawns a background watcher agent plus a 30-minute watchdog cron that re-invoke the review round whenever the author hands the work back, pushes new code, or the pipeline settles. - Finding ledger and thread resolution: Maintains a persistent ledger of every finding with status (open, addressed, refuted, superseded), revisits every open thread each round, and resolves or un-resolves only its own threads based on code evidence. - Use Case: A reviewer asks Claude to watch MR !123. The Skill reviews the branch, posts findings, moves the ticket to the work state, then automatically re-reviews each new push until nothing remains open. ## Quick Start Ask Claude to review the current branch's merge request and watch it until all findings are addressed or refuted.

Frequently Asked Questions about watch

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

FAQPage Schema
How do I watch a GitLab merge request until the review is settled?▼

Invoke the watch command on the branch's MR. It runs a full review, posts findings, hands the work back to the author, and spawns the glab:mr-watch agent that re-triggers review rounds whenever the author hands the work back or pushes new code.

How does the review handshake work between reviewer and author?▼

The handshake is paced by the ticket state defined in teamwork:review-handshake. After posting findings the reviewer moves the ticket to the work state; a new round starts only when the ticket returns to the review state, or via a push gate when no tracker exists.

Can this command push fixes or rebase the branch locally?▼

No. The reviewer stance forbids editing code, committing, pushing, or local rebases. The only authorized git writes are one server-side rebase via glab mr rebase and a guarded git reset --hard that syncs the local checkout onto the author's remote head.

What tools are required to run the MR watch workflow?▼

It requires the glab CLI plus the glab-discussion and glab-pipeline tools, installable with uv tool install glab-discussion glab-pipeline. It also depends on the glab and teamwork plugins for the mr-status, mr-watch, workflow-identify, and review-handshake skills.

What happens when the server-side rebase of an MR fails?▼

The rebase is attempted exactly once and never retried. On failure, such as conflicts or missing push access, the exact error is recorded as a Blocking finding for the author, and the review proceeds against the un-rebased head without any local rebase.

When does the MR watch stop running?▼

The watch terminates when no blocking or suggestion findings remain open, when the MR is merged or closed, or when the idle cap is exceeded. The watcher agent and watchdog cron are then stopped and the ticket is left in the appropriate state.