01
What this skill does
Use this skill when creating, previewing, configuring, troubleshooting, installing, updating, uninstalling, or maintaining Git merge requests or pull requests through the `mr`, `mrm`, `mrt`, and `mrp` commands. It keeps agents aligned with the CLI's real request-provider behavior, non-blocking update notices, and resume paths for inline and detached conflicts instead of inventing manual git recovery steps.
02
When to use it
- 01Creating or previewing Git merge requests or pull requests from a current branch to master, test, prerelease, or an arbitrary target.
- 02Checking for a missing local mr install and installing it after user confirmation.
- 03Choosing between merge, rebase, merge-target, direct PR, and default detached-mode workflows.
- 04Configuring CNB, GitHub, GitLab, or custom request commands for pushed source branches.
- 05Understanding automatic update notices and the environment variables that disable them.
- 06Handling stopped merge or rebase states while preserving the CLI-owned resume path.
- 07Maintaining the TypeScript/Pastel/Ink/Zod implementation behind the CLI.
03
How it works
- 01
Inspect repository state with `git status --short --branch` before mutating MR branches.
- 02
Check `command -v mr` before running CLI-dependent workflows; if missing, ask before installing unless the user explicitly requested install.
- 03
Resolve target aliases and clarify source, target, and MR-branch keep/delete intent before acting on ambiguous MR requests.
- 04
Use `--dry-run` when strategy, detached mode, or repository state is unclear.
- 05
Run exactly one strategy and respect config precedence for strategy, detached mode, request provider, and custom request command settings.
- 06
Treat interactive update notices as informational stderr, not workflow output or command failures.
- 07
On conflicts, hand off resolution to the user and then rerun the matching `mr` resume command only after conflicts are staged.
- 08
When editing the CLI project, verify the implementation repository instead of assuming a local path, and keep README behavior, command examples, and diagrams aligned with implementation changes.
04
What you get back
- 01Safe command choices for `mr`, `mrm`, `mrt`, and `mrp` workflows.
- 02Update-notice interpretation and disablement guidance.
- 03Conflict handoff and resume instructions that match the current CLI implementation.
- 04Scoped maintenance guidance and verification commands for the mr project.
05
Important boundaries
- 01Do not combine strategy flags or use `--rm-mr` with `--pr`.
- 02Do not replace CLI conflict resume with hand-written git commits, manual pushes, or a shortcut `--pr` flow.
- 03Do not mutate stopped merge/rebase states unless the user explicitly asks for that exact action.
06