What problem does it solve? Reviewing a GitLab merge request requires different artifacts for different audiences: a plain-language summary for stakeholders, a detailed diff for reviewers, and a focused test plan for QA. Manually assembling all three from an MR is slow and inconsistent. ## Core Features & Use Cases - Three-audience HTML page: Builds one self-contained HTML file with exactly three tabs — a plain-language Summary (with a rollback section when migrations are present), a per-file collapsible Diff tab with "what changed and why" notes, and a QA tab written in user-action language with automated-coverage verdicts and checkbox checklists. - QA coverage discovery: Partitions changed files into production and non-production, then runs a same-MR diff check, path-mirror lookup, and symbol grep to assign each changed area an automated / partly automated / not automated / unknown verdict. - Graceful degradation: Works without a local clone of the project (QA tab degrades with a banner), falls back from GitLab MCP to the glab CLI, and renders Jira links as plain spans when Atlassian is unavailable. - Use Case: A reviewer runs the skill on MR !4830, receives a single HTML file, drops it in Slack — the PM reads the Summary tab, the QA engineer works only from the QA tab checklists. ## Quick Start Run /mr-review-companion and paste a GitLab merge request URL to generate the review HTML page.
