git-master

Coordinate Git workflows for atomic commits, interactive rebasing, and history cleanup.

32.6k|2.5k|Updated Feb 2, 2026

Search Tags:#git #branch-management #atomic-commits #version-control #interactive-rebase #history-cleanup

Ready to run

npx skills add https://github.com/Yeachan-Heo/oh-my-codex --skill git-master-yeachan-heo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/Yeachan-Heo/oh-my-codex/tree/main/skills/git-master
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-codex --skill git-master-yeachan-heo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill coordinates advanced Git workflows to ensure atomic commits, clean rebases, and maintainable history across branches, reducing manual teardown and confusion in collaborative projects.

Core Features & Use Cases

Atomic commits with conventional format to ensure traceable changes.
Interactive rebasing and branch management to tidy up commit history before merging.
History cleanup and style detection from repository history to enforce consistency and readability.

Quick Start

Run the git-master agent to perform an atomic commit, start an interactive rebase, and tidy the branch history.

Frequently Asked Questions about git-master

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

FAQPage Schema

What is an atomic commit in Git and when do I need it?▼

Use interactive rebasing to tidy commit history by rewriting, squashing, or reordering commits before merging. This coordinates branch management to ensure a clean, maintainable history across feature branches.

How do I clean up my Git branch history before a pull request?▼

Yes, history cleanup coordinates branch management for small to large repositories. It handles feature branches and pull requests by enforcing conventional commit formats and consistency across the repository.

Do I need any dependencies to perform interactive rebasing and history cleanup?▼

No dependencies are required. The workflow routes to the git-master agent with model configuration and prompt templates to perform interactive rebasing and history cleanup without external tool installations.

What's the best way to manage feature branches and maintain history hygiene in large repositories?▼

The best way is coordinating Git workflows for atomic commits, interactive rebasing, and history maintenance. This reduces manual teardown and confusion, ensuring maintainable history across branches in large repositories.