Setup
Configure GitLab MR Guardian by persisting the hostname and safety options into the plugin data directory, then verify glab authentication and run a read-only status check. Use when the user asks to initialize, enable, or change automatic MR monitoring, rebasing, auto-merge, project filters, or the GitLab host.From its SKILL.md
npx -y skills add MisterRaindrop/gitlab-mr-guardian --skill setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.2 KB, as published. Nobody here has run it
Set up GitLab MR Guardian
-
Show the currently effective configuration and monitor switch:
"${CLAUDE_PLUGIN_ROOT}/bin/gitlab-mr-guardian" \ --plugin-data-dir "${CLAUDE_PLUGIN_DATA}" \ configureThe
CONFIG_SHOWoutput includesconfig(effective values) andmonitor_enabled(the real persistent background-polling switch). -
Determine the GitLab hostname: use
$ARGUMENTSwhen supplied; otherwise keep the already-configured hostname when it is non-empty; otherwise infer it fromgit remote get-url origin; otherwise ask the user. -
Run
glab auth status --hostname <hostname>. If it reports a token problem, do not stop there: confirm with a real read call such asglab api user --hostname <hostname>, becauseglab auth statuscan report an invalid token while API access still works. Never print or request an access token whenglabAPI calls succeed. Warn the user that write operations (rebase, pipeline trigger, auto-merge) may still fail if the token lacksapiscope. -
Explain the two mutation switches:
auto_rebaseis on by default and rewrites the source branch, but only when GitLab reportsneed_rebaseand the MR is managed (offer--auto-rebase falseto users who do not want it). Note that a rebase is allowed by default even when it clears existing approvals, because a managed MR has already been reviewed; mention--allow-rebase-that-resets-approvals falseto anyone who needs those approvals preserved.auto_mergeis off by default and can merge code immediately once all guarded checks pass; obtain confirmation before enabling it unless the user already explicitly requested it in the current turn. -
Persist the configuration into the plugin data directory. Pass only the options the user chose to set; omitted options keep their previous or default values:
"${CLAUDE_PLUGIN_ROOT}/bin/gitlab-mr-guardian" \ --plugin-data-dir "${CLAUDE_PLUGIN_DATA}" \ configure \ --hostname "<hostname>"This writes
settings.jsoninside${CLAUDE_PLUGIN_DATA}. The background monitor and all other commands read configuration from this file; native plugin userConfig substitution is not used. Never create or edit configuration inside the user's repository.Blocker-clearing rules are on by default, because a managed MR has already passed human review:
max_pipeline_retries(retry a failed pipeline's jobs up to 10 times, one attempt per polling cycle),rebase_when_ci_failed(allow safe rebase forneed_rebaseMRs while CI is not yet successful — failed, running, missing, or skipped; a running pipeline on the stale base is superseded),allow_rebase_that_resets_approvalsandallow_rebase_when_approval_policy_unknown(rebase even when it would clear approvals or the approval policy cannot be read). Turn any of them off with--<flag> falsewhen the user wants a more conservative posture — for example--allow-rebase-that-resets-approvals falseto preserve approvals.Optional extensions that are off by default:
--require-successful-pipeline-history true(restrict management to approved MRs whose history already shows a successful pipeline; by default approval alone is enough) and--advisory-reviewers <bot,names>(comma-separated usernames, e.g. AI review bots, whose unresolved discussions are advisory and never block automation). Explain the behavior change and confirm before enabling either unless the user already explicitly requested it.Polling visibility: quiet cycles report a
MONITOR_HEARTBEATby default, so a silent Monitor is distinguishable from a dead one. Every heartbeat wakes the session, so when the user sets a shortpoll_interval_seconds, point out--heartbeat-min-interval-seconds <seconds>to throttle idle reports (real events always report immediately regardless), or--heartbeat-when-idle falseto silence them entirely and rely onmonitor.last_cycleinstatus. -
Run a read-only status check and summarize which merge requests are monitored, paused for review, waiting for CI, or blocked:
"${CLAUDE_PLUGIN_ROOT}/bin/gitlab-mr-guardian" \ --plugin-data-dir "${CLAUDE_PLUGIN_DATA}" \ status -
Report the real monitoring state from the
monitor_enabledfield of theCONFIG_SAVEDoutput — do not assume polling is off. If it istrue, background polling is already active and will pick up the new configuration on its next cycle. If it isfalse, tell the user that/gitlab-mr-guardian:startenables background polling and/gitlab-mr-guardian:stopdisables it; polling runs only while an interactive Claude Code session is open.
Do not weaken the approval or unresolved-discussion checks — those still gate every mutation. allow_rebase_that_resets_approvals is on by default, so tell the user a rebase can invalidate approvals and set it to false when they want them preserved.