Menu
Push current branch, create MR/PR on GitHub, GitLab, or Forgejo, wait for CI pipeline, merge, and clean up branch using auto-mr CLI
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Detect repository hosting service (GitHub/GitLab/Forgejo) from git remote and extract owner/repo/project_path. Internal utility skill used by commands that need platform-aware routing.
Scaffold the Bulma CSS framework into a Go web app with embedded assets for zero-dependency binaries. Internal skill used by golang-pro agent when building HTML UIs with a classes-based CSS framework and no Node toolchain.
Manage Go tool dependencies using the tool directive (Go 1.24+). Use when a Go project needs code generation tools like sqlc, moq, templ, swag, or stringer managed as reproducible Go tool dependencies.
Integrate Charmbracelet gum for beautiful, TTY-safe terminal output in bash scripts. Internal skill used by bash-pro agent for interactive prompts, styled output, and structured logging.
Detect white box Go tests and propose conversion to black box tests (package foo_test). Internal skill used by golang-pro agent to enforce black box testing conventions.
Recommend and scaffold Go project layouts based on project type (CLI, API, library, monorepo). Internal skill used by golang-pro agent when initializing projects or reviewing structure.
| name | auto-mr |
| description | Push current branch, create MR/PR on GitHub, GitLab, or Forgejo, wait for CI pipeline, merge, and clean up branch using auto-mr CLI |
| argument-hint | [--no-squash] [--msg "text"] [--labels "label1,label2"] [--list-labels] [--pipeline-timeout "30m"] [--log-level debug|info|warn|error] |
| user-invocable | true |
| allowed-tools | Bash(auto-mr:*), Bash(git:*), AskUserQuestion |
Push the current branch, create a MR/PR on GitHub, GitLab, or Forgejo, wait for the CI pipeline, merge, and clean up the branch — all via the auto-mr CLI.
For git.sylvlab.fr repositories, the underlying auto-mr binary routes via the fgj CLI; GitHub and GitLab remotes are handled automatically as before. Platform detection and routing are handled entirely by the binary — this skill does not branch on the host.
Flags:
--labels string Comma-separated label names (e.g., "bug,enhancement")
--list-labels List all available labels and exit
-l, --log-level string Set log level (debug, info, warn, error) [default "info"]
--msg string Custom message for MR/PR (overrides commit message selection)
--no-squash Disable squash merge (default: squash enabled)
--pipeline-timeout string Pipeline/workflow timeout [default "30m"]
-v, --version Print version and exit
Verify auto-mr is installed:
auto-mr --version
If the command fails, abort with:
auto-mris not installed. Install it from https://github.com/sgaunet/auto-mr and ensure it is in your PATH.
Get current branch:
git rev-parse --abbrev-ref HEAD
If the branch is main, master, or develop, warn the user:
Warning: you are on a protected branch (
<branch>).auto-mris intended for feature branches.
Check for uncommitted changes:
git status --porcelain
If the working tree is dirty, warn the user:
Warning: you have uncommitted changes. Consider committing or stashing them before creating a MR/PR.
If --list-labels is present in the arguments:
auto-mr --list-labels
Display the output and return. Do not proceed further.
Base command: auto-mr
Append all provided flags verbatim (e.g., --no-squash, --msg "fix: ...", --labels "bug,help wanted").
If a working_directory context is provided, prefix with cd <working_directory> &&.
Display a summary to the user:
Branch: <current-branch>
Command: <assembled-command>
Ask the user to confirm via AskUserQuestion:
Proceed with the above command? (yes/no)
If the user declines, abort gracefully.
Run the assembled command. auto-mr handles the full flow:
On success: display the output (includes the MR/PR URL).
On failure: display the error output, then suggest the manual fallback:
git push -u origin <branch>
# Then open a MR/PR via the repository web UI
If a working_directory context is provided (e.g., a worktree path from feature-flow-w), prefix all commands with cd <working_directory> &&. Otherwise, use the current directory.