How do I install the Auto Mr skill?

Run npx skillmds@latest add sgaunet/auto-mr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Auto Mr safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Auto Mr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Auto Mr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Auto Mr?

sgaunet (@sgaunet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Auto Mr by sgaunet — Agent Skill

Name: Auto Mr
Rating: 4.2 (5 reviews)
Author: sgaunet

File contents

auto-mr Skill

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.

CLI Reference

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

Workflow

Step 1: Pre-flight Checks

Verify auto-mr is installed:

auto-mr --version

If the command fails, abort with:

auto-mr is 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-mr is 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.

Step 2: Label Discovery (early exit)

If --list-labels is present in the arguments:

auto-mr --list-labels

Display the output and return. Do not proceed further.

Step 3: Assemble Command

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> &&.

Step 4: Confirm Before Executing

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.

Step 5: Execute

Run the assembled command. auto-mr handles the full flow:

Push branch to remote
Create MR (GitLab) or PR (GitHub/Forgejo)
Wait for CI pipeline/checks
Merge when CI passes
Delete the remote branch

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

Working Directory

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.

---name: auto-mrdescription: Push current branch, create MR/PR on GitHub, GitLab, or Forgejo, wait for CI pipeline, merge, and clean up branch using auto-mr CLI---# auto-mr SkillPush 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.## CLI Reference```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```## Workflow### Step 1: Pre-flight Checks**Verify `auto-mr` is installed:**```bashauto-mr --version```If the command fails, abort with:> `auto-mr` is not installed. Install it from https://github.com/sgaunet/auto-mr and ensure it is in your PATH.**Get current branch:**```bashgit 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-mr` is intended for feature branches.**Check for uncommitted changes:**```bashgit 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.### Step 2: Label Discovery (early exit)If `--list-labels` is present in the arguments:```bashauto-mr --list-labels```Display the output and return. Do not proceed further.### Step 3: Assemble CommandBase 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> &&`.### Step 4: Confirm Before ExecutingDisplay 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.### Step 5: ExecuteRun the assembled command. `auto-mr` handles the full flow:1. Push branch to remote2. Create MR (GitLab) or PR (GitHub/Forgejo)3. Wait for CI pipeline/checks4. Merge when CI passes5. Delete the remote branch**On success:** display the output (includes the MR/PR URL).**On failure:** display the error output, then suggest the manual fallback:```bashgit push -u origin <branch># Then open a MR/PR via the repository web UI```## Working DirectoryIf 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.

Frequently asked questions

Auto Mr