GitLab Skill

This skill provides GitLab operations using the glab CLI. It handles three operations based on the user's request.

Operation 1: Push to Branch

When the user asks to push to a branch or push their changes to GitLab:

1. Get the current branch if none is specified:

   git branch --show-current
   

2. Push to the remote, setting upstream tracking on first push:

   git push -u origin <branch>
   

3. Report success and show the branch URL if glab outputs it.

Operation 2: Create Merge Request

When the user asks to create an MR or merge request:

1. If the user has not specified a title, ask for one before proceeding.

2. Create the MR using glab:

   glab mr create \
     --title "<title>" \
     --description "<description>" \
     --target-branch <main or master, detect from repo> \
     --fill
   

   • Use --fill to populate description from commit messages when appropriate.
   • Omit --description if the user did not provide one (let --fill handle it).
   • Do not mark as draft unless the user requests it.

3. Display the MR URL from the command output.

Operation 3: Get MR Comments

When the user asks to see, fetch, or list comments or notes on a merge request:

1. If an MR ID or branch name is given, use it directly:

   glab mr note list <mr-iid>
   

2. If no ID is given, detect the MR for the current branch:

   glab mr list --source-branch "$(git branch --show-current)"
   

   Extract the MR IID from the output, then:

   glab mr note list <mr-iid>
   

3. Present the comments clearly: show the author, timestamp, and body for each note.

Notes

• Always confirm glab is authenticated before operations if errors occur: glab auth status
• For push errors due to no upstream, use git push -u origin <branch> (the -u flag is included by default above)
• When the target branch for MR creation is ambiguous, check git remote show origin or ask the user