Verified:GitHub

mr-creation

Automates merge request creation across multiple Git repositories via GitLab API and repo tool.

Updated Feb 10, 2026

Search Tags:#automation #git #workflow #gitlab #merge request #repo tool

One-click install

npx skills add https://github.com/tardyp/esp_tock --skill mr-creation

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: mr-creation
Source: https://github.com/tardyp/esp_tock/tree/main/.opencode/skills/mr-creation
Command: npx skills add https://github.com/tardyp/esp_tock --skill mr-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires repo, git, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of creating merge requests across numerous Git repositories simultaneously, ensuring consistency and efficiency in large-scale code changes.

Core Features & Use Cases

Automated MR Generation: Creates merge requests for multiple repositories with a single command.
Workflow Orchestration: Guides users through identifying modified repositories, committing changes, branching, pushing, and finally creating MRs via the GitLab API.
Use Case: When migrating a shared library or updating a common dependency across dozens of microservices, this Skill ensures all necessary MRs are created systematically, reducing manual effort and potential errors.

Quick Start

Use the mr-creation skill to automate the creation of merge requests for your recent code changes across multiple repositories.

Frequently Asked Questions about mr-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create merge requests across multiple GitLab repositories at once?▼

You can automate merge requests across multiple GitLab repositories by using the repo tool alongside a Python script that interacts with the GitLab API. This orchestrates branching, pushing, and MR creation systematically for coordinated updates.

What is the best way to manage dependency updates across many microservices?▼

Managing dependency updates across microservices is best handled by automating merge request generation for all affected repositories. This ensures all necessary MRs are created systematically, reducing manual effort and potential errors during migrations.

Do I need a GitLab Personal Access Token to automate merge request creation?▼

Yes, you need a GitLab Personal Access Token with API scope to automate merge request creation. The Python script uses this token to authenticate with the GitLab API when pushing changes and opening merge requests.

Can I use the repo tool to coordinate catalog migrations across a monorepo?▼

Yes, you can use the repo tool to coordinate catalog migrations across a monorepo or related repositories. It identifies modified repositories, commits changes, branches, pushes, and creates merge requests via the GitLab API.

What dependencies are required to automate multi-repo merge request workflows?▼

Automating multi-repo merge request workflows requires the repo tool, Git, and Python3 installed. These dependencies allow the script to orchestrate repository changes and interact with the GitLab API.

When should I avoid automating merge requests across multiple repositories?▼

You should avoid automating merge requests across multiple repositories if your changes are isolated to a single repository or if you lack a GitLab Personal Access Token with API scope, as the workflow relies on the repo tool for coordinated updates.