git-master

Create atomic Git commits with conventional formatting and manage repository history.

20|6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill git-master-realsigridjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/git-master
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill git-master-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps manage complex Git workflows without creating messy commits, risky history changes, or inconsistent branch practices.

Core Features & Use Cases

  • Atomic Commits: Organize changes into focused commits using conventional formatting.
  • History Management: Handle interactive rebasing, branch management, and history cleanup.
  • Repository-Aware Workflows: Detect existing repository style and apply appropriate Git practices when preparing changes for review or collaboration.

Quick Start

Ask the git-master skill to create atomic commits for the current changes and clean up the branch history.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I create atomic git commits with conventional formatting?

Atomic git commits group related changes into focused, self-contained units. This Skill analyzes current changes and applies conventional formatting to ensure repository history remains clean, reviewable, and reliable for collaboration.

What is the best way to clean up messy git branch history?

Cleaning up git branch history requires interactive rebasing to safely reorder, squash, or edit commits. This Skill manages repository-aware workflows to clean branches without risky history changes or inconsistent practices.

How does interactive rebasing work for managing repository history?

Interactive rebasing modifies previous commits by changing their order, squashing them, or altering messages. This Skill handles interactive rebasing to apply safe, focused version-control operations for history cleanup.

Can I use this for branch management across different repository styles?

Yes, branch management works across different repository styles. This Skill detects existing repository style and applies appropriate Git practices to maintain consistent branch management and atomic commit organization.

Why do I need atomic commits for preparing changes for review?

Atomic commits isolate distinct logical changes, making code review easier and rollback safer. This Skill prepares changes for review by interpreting repository history and organizing changes into focused, conventional commits.