What problem does it solve? When working with GitLab merge requests, developers must manually check pipeline results, review discussion threads, and track external commit statuses across multiple tools to understand what blocks a merge. This Skill consolidates that state into a single read-only report. ## Core Features & Use Cases - Pipeline Inspection: Reads the pre-generated pipeline summary to identify failed jobs, their stages, and failure reasons, pointing to the exact log or report file that explains each failure. - Discussion Review: Reads dumped discussion thread files to surface unresolved comments and highlights changes since the last run. - Merge Blocker Summary: Covers external commit statuses and states exactly what blocks the merge right now, without taking any action or changing code. - Use Case: After pushing changes to an MR, ask for an overview to see which jobs failed, which review threads are still open, and whether external statuses are green before handing the MR back to reviewers. ## Quick Start Ask the assistant to show the overview of the current merge request, including pipeline failures, open discussions, and what is blocking the merge.
