commit-push-open-mr

Review, stage, commit, push, and open or update merge requests on GitHub or GitLab.

2|1|Updated Jul 3, 2012

Search Tags:#git #workflow #commit #code-review #pull-request #merge-request

One-click install

npx skills add https://github.com/Yasumoto/joe-dotfiles --skill commit-push-open-mr

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: commit-push-open-mr
Source: https://github.com/Yasumoto/joe-dotfiles/tree/main/dotfiles/claude/skills/commit-push-open-mr
Command: npx skills add https://github.com/Yasumoto/joe-dotfiles --skill commit-push-open-mr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers through a disciplined Git workflow to review changes, commit them with meaningful messages, push to origin, and open or update a merge/pull request, reducing manual steps and improving collaboration.

Core Features & Use Cases

Review git status and identify changes that belong to a single logical commit.
Stage and commit changes with a clear, conventional message, then push to the remote repository.
Open or update a merge/pull request using GitHub or GitLab tooling, optionally assigning reviewers or linking related issues.
Coordinate code reviews and maintain a clean history across teams.

Quick Start

Review the current branch, stage only relevant changes, commit with a clear message, push to origin, and open or update the MR/PR.

Frequently Asked Questions about commit-push-open-mr

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

FAQPage Schema

How do I automate committing, pushing, and opening a merge request in a Git workflow?▼

Automating a Git workflow for merge requests involves reviewing git status, staging logical changes, committing with clear messages, pushing to origin, and opening or updating the request using standard git commands and tooling.

Does this workflow support both GitHub pull requests and GitLab merge requests?▼

Yes, the workflow supports GitHub pull requests and GitLab merge requests by relying on standard Git commands alongside either the gh or glab command-line tooling to manage code reviews and request creation.

What's the best way to group code changes before committing and opening a pull request?▼

The best way to group changes before committing and opening a pull request is to review the current git status, identify modifications belonging to a single logical commit, and stage only those relevant changes before pushing.

Can I assign reviewers and link related issues when opening a merge request?▼

Yes, you can assign reviewers and link related issues when opening or updating a merge request, coordinating code reviews by passing options through the underlying GitHub or GitLab tooling.

How does a disciplined commit history improve code reviews on remote repositories?▼

A disciplined commit history improves code reviews by ensuring changes are grouped logically with clear, conventional messages, making it easier for teams to coordinate and track modifications across remote repositories.

Do I need to install the gh or glab CLI tools to automate pull request creation?▼

Yes, you need to install either the gh or glab CLI tools to automate pull request creation, as the workflow relies on these platform-specific tools to manage and update requests on GitHub or GitLab.