commit-and-mr

Automates GitLab merge request creation with git-blame reviewers and optional Jira keys.

4|Updated Apr 10, 2023

Search Tags:#commit #branching #gitlab #reviewers #merge-request #conventional-commits #git-blame

One-click install

npx skills add https://github.com/dudeofawesome/nix-config --skill commit-and-mr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: commit-and-mr
Source: https://github.com/dudeofawesome/nix-config/tree/main/modules/presets/home-manager/paciolan/llms/skills/commit-and-mr
Command: npx skills add https://github.com/dudeofawesome/nix-config --skill commit-and-mr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Commit and push changes to a development branch, then generate a GitLab merge request with reviewers automatically selected from git blame.

Core Features & Use Cases

Branch management: creates and checks out a feature branch when needed and stages changes with conventional commits.
Reviewer discovery: automatically resolves reviewers from git blame and adds them to the MR.
Jira integration: optionally ties a Jira key to the MR description and lifecycle.

Quick Start

Commit and push your current changes, then open a GitLab merge request with reviewers selected from git blame.

Frequently Asked Questions about commit-and-mr

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

FAQPage Schema

How do I automate a GitLab merge request and assign reviewers from git blame?▼

You can automate a GitLab merge request by committing changes, pushing to a branch, and resolving reviewers from git blame. This workflow handles branching, conventional commits, and MR creation automatically.

How do I link a Jira key to a GitLab merge request automatically?▼

To link a Jira key, you pass it as a parameter during the workflow. The process validates the Jira key, attaches it to the MR description, and ties it to the merge request lifecycle.

Can I use conventional commits to automate branch creation and pushing to GitLab?▼

Yes, you can use conventional commits to stage changes and push to GitLab. The workflow creates and checks out a feature branch when needed, stages your changes, and handles push errors with retry logic.

How does git blame resolve reviewers for a merge request?▼

Git blame resolves reviewers by analyzing the commit history of the files you changed. It automatically identifies the developers responsible for previous lines of code and adds them as reviewers to the MR.

Do I need glab to automate opening a GitLab merge request with conventional commits?▼

Yes, you need glab installed to open a GitLab merge request through this workflow. The automation relies on standard tools like git and glab to handle branching, pushing, and MR creation.

What happens when push errors occur during the automated git workflow?▼

When push errors occur during the git workflow, the automation handles them with retry logic. This maintains a smooth workflow by attempting to resolve push failures automatically before proceeding to MR creation.