What problem does it solve? Merge request descriptions often bury reviewers in process noise, chat transcripts, and restated diffs, making it hard to tell what changed and why. This Skill produces descriptions a reviewer can act on: a one-paragraph TLDR, a body naming the defect and fix, and nothing else. ## Core Features & Use Cases - Author-voice writing: The description reads as written by the human whose name is on the request, with no mention of the agent, session, or chat transcripts. - TLDR-first structure: Every description opens with a single short paragraph stating what the change does and why, followed by a concrete body naming the defect, cause, and fix. - Commit-derived content: Reasoning is pulled from git log on the working branch before writing, and the request is opened from a dedicated mr/ branch squashed to one commit whose message is the description. - Conditional collapsible blocks: A <details> section is allowed only for evidence the commits cannot carry, such as a captured upgrade log, under three strict conditions. - Use Case: After finishing a bug fix on a feature branch, ask the agent to open the merge request; it reads the branch commits, writes the TLDR and body, cuts an mr/ branch, squashes, and pushes. ## Quick Start Write the merge request description for my current branch and open it from a squashed mr/ branch.
