Verified:GitHub

git-ops

Automate Git commits, branch pushes, and GitHub PR or GitLab MR creation.

Updated Dec 5, 2025

Search Tags:#automation #git #devops #pull request #commits #merge request

Ready to run

npx skills add https://github.com/bponghneng/rouge --skill git-ops-bponghneng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-ops
Source: https://github.com/bponghneng/rouge/tree/main/.agents/skills/git-ops
Command: npx skills add https://github.com/bponghneng/rouge --skill git-ops-bponghneng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating well-formatted Git commits and opening pull/merge requests, saving developers time and ensuring consistency.

Core Features & Use Cases

Conventional Commits: Automatically generates commits following the conventional commit standard.
Branch Pushing: Pushes the current branch to its remote origin.
PR/MR Creation: Creates GitHub Pull Requests or GitLab Merge Requests with drafted titles and summaries.
Use Case: After completing a feature, use this skill to group your changes into logical commits, push your branch, and open a PR, all with a single command.

Quick Start

Use the git-ops skill to compose commits and open a pull request for the current branch.

Frequently Asked Questions about git-ops

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

FAQPage Schema

How do I automate git commits and pull requests in one step?▼

To automate git commits and pull requests, you can group changes into conventional commits, push the branch to origin, and open a GitHub PR or GitLab MR with a single command. This skill drafts titles and summaries automatically.

What is a conventional commit and how does automation handle it?▼

A conventional commit follows a structured message standard for readable history. This automation generates these formatted commit messages automatically, grouping your staged changes logically without manual message drafting.

Do I need GitHub CLI or GitLab CLI to create merge requests with automation?▼

Yes, creating merge requests or pull requests requires the GitLab CLI (glab) or GitHub CLI (gh) installed respectively. The core Git CLI is always required for local operations and branch pushing.

Can I push a git branch to origin and open a GitLab merge request together?▼

Yes, you can push a branch to origin and open a GitLab merge request together. The skill supports combined workflows that automate branch pushing and MR creation with drafted summaries in one sequence.

What is the best way to group changes before pushing a feature branch?▼

The best way to group changes before pushing is using commit grouping automation. This process organizes your working changes into logical conventional commits before pushing the branch to remote origin.

Does automated PR creation work with both GitHub and GitLab?▼

Automated PR creation works with both GitHub and GitLab. It uses GitHub CLI for pull requests and GitLab CLI for merge requests, drafting titles and summaries for either platform based on your installed CLI.