What problem does it solve? Opening a merge request often scatters context: the reasoning ends up in the description, review guidance gets lost, and release steps are never written down. This Skill opens a draft MR for the current branch and places each piece of information where it belongs — the Why in the ticket, discussion topics in separate MR comment threads, and a short summary in the description. ## Core Features & Use Cases - Structured MR creation: Pushes the branch, opens a draft MR/PR via the host's CLI (GitLab, GitHub), and reuses an existing MR if one is already open for the branch. - Content placement rules: Writes the problem and approach into the ticket, posts reviewer guidelines, release procedure, and verification results as standalone MR discussion threads, and keeps the description under a 12-line cap with just the ticket link and summary. - Reviewer guidance with diagrams: Highlights load-bearing diff sections with file:line pointers and can include a validated mermaid diagram for flows crossing multiple components. - Use Case: After finishing a feature branch, run the command with a ticket ID to open a draft GitLab MR whose description links the ticket, whose comments guide the reviewer through the diff, and whose release thread documents migration ordering. ## Quick Start Open a draft MR for my current branch with ticket PROJ-123, putting the reasoning in the ticket and a reviewer guide in the MR comments.
