create-mr
Create a new merge request in a GitLab project
What this skill does
# Create GitLab Merge Request ## Name gitlab:create-mr - Create a new merge request in a GitLab project ## Synopsis ``` /create-mr [arguments] ``` ## Description Create a new merge request in a GitLab project ## Implementation Create a new merge request in a GitLab project with source and target branches. ## Usage ``` /create-mr ``` This command helps you create a merge request with all necessary details. ## What This Command Does 1. Asks for the project ID or path 2. Prompts for source branch name 3. Requests target branch name 4. Asks for MR title 5. Requests MR description (optional) 6. Creates the merge request using the GitLab MCP `create_merge_request` tool 7. Returns the MR number and URL ## Prerequisites - GitLab MCP server must be installed and configured - GitLab version 18.5 or later - You must have Developer or higher role in the project - Both source and target branches must exist - OAuth authentication must be completed ## Example Interaction ``` User: /create-mr Claude: I'll help you create a merge request. What's the project ID or path? User: 456 Claude: What's the source branch name? User: feature/user-authentication Claude: What's the target branch name? User: main Claude: What should the merge request title be? User: Add JWT-based user authentication Claude: Please provide a description (optional, press Enter to skip): User: This MR implements JWT-based authentication for the API: - User login and registration endpoints - Token generation and validation middleware - Password hashing with bcrypt - Unit tests for auth flows Closes #42 Claude: Creating merge request in project 456... ✓ Merge request created successfully! !15 - Add JWT-based user authentication https://gitlab.com/your-org/project/-/merge_requests/15 Status: Open Source: feature/user-authentication Target: main ``` ## Tips - Link related issues using `Closes #123` or `Fixes #123` in the description - Use conventional commit prefixes in titles: `feat:`, `fix:`, `refactor:` - Include a testing checklist in the description - Add reviewers after creation if needed - Set appropriate labels for categorization - Consider creating a draft MR for work-in-progress ## Related Commands - `/view-mr`: View merge request details and diffs - `/review-mr`: Get a comprehensive review of a merge request - `/create-issue`: Create an issue that this MR will resolve
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.