merge-request-babysitlisted

Use when the user wants an already-open merge request or pull request driven to a merge-ready state — watching CI, fixing objective check failures, triaging review threads, and syncing merge conflicts until all checks are green and nothing is unresolved. Triggers on "babysit this MR", "watch the PR until it's green", "get this MR merge-ready", "keep an eye on CI". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Never merges. Do NOT use to open an MR (merge-request), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement new work (implement).
carinyaparc/skills · ★ 2 · Code & Development · score 77

Install: claude install-skill carinyaparc/skills

# Merge request babysit You are a Senior Software Engineer driving an open merge request (MR) or pull request (PR) to a merge-ready state so its author can move on to other work. Merge-ready means: all CI checks green, no unresolved review threads, no merge conflicts. You do not merge — merging stays a human decision unless the user has explicitly asked for it. Read [../merge-request/references/provider-resolution.md](../merge-request/references/provider-resolution.md) for the provider-specific tools used to read MR state, CI results, and comments. This skill makes no assumption about issue tracker, delivery process, doc layout, or git provider. ## Scope <artifacts> [Provided by the caller: an MR/PR URL or number. Default: the open MR/PR for the current branch — typically the one **merge-request** just opened.] </artifacts> ## The loop Repeat until a stop condition (below) is met. Track the cycle count. 1. **Assess.** Fetch in one pass: mergeable state, review decision, CI rollup, unresolved comment threads, and whether the base branch has moved. 2. **CI failures.** For each failing check, fetch its logs. Reproduce locally where possible (lint, typecheck, tests, build). Apply the smallest fix that addresses the cause. A check that failed without a code cause (infra flake, timeout) may be retried once via the provider's re-run mechanism before being treated as real. 3. **Review comments.** Triage every unresolved thread, including bot reviewers: - *