skills.rest
chanhee-kang
chanhee-kangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-master

Split and reorder Git commits into atomic changes with safe rebasing.

2|Updated Feb 3, 2026
Search Tags:#git#workflow#atomic-commits#version-control#rebasing#history-management
One-click install
npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill git-master-chanhee-kang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/chanhee-kang/oh-my-gemini/tree/main/skills/git-master
Command: npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill git-master-chanhee-kang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces disciplined Git practices for atomic commits, history rewriting, and systematic change tracking.

Core Features & Use Cases

  • Atomic commits with proper grouping of changes
  • History rewriting safety guidelines for rebasing
  • Commit-splitting decisions based on components, directories, or concerns
  • History search commands to trace when changes were introduced
  • Safe branch management and structured code reviews

Quick Start

Use this skill to help plan and implement a clean, atomic-commit history across feature development cycles. For example, prompt the AI to outline how to split a large feature into atomic commits and perform an interactive rebase to clean up history.

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split a large feature into atomic commits in git?▼

To split a large feature into atomic commits, group changes by components, directories, or concerns. This ensures precise commit granularity and a clean history, making it easier to trace when changes were introduced.

What is the safest way to rewrite git history with rebasing?▼

Safe git history rewriting requires interactive rebasing operations to reorder or clean up commits without deleting work. Following structured history management guidelines prevents data loss during iterative cleanup on feature branches.

How do I trace when a specific change was introduced using git?▼

Trace when changes were introduced using standard history search commands like git log, git blame, and git bisect. These tools analyze history to pinpoint exactly when and why specific multi-file changes occurred.

Do I need special tools to manage version control tasks and feature branches?▼

No special tools are needed beyond standard Git commands and basic shell access. You can perform systematic change tracking, safe branch management, and structured code reviews using your existing version control environment.

What's the best way to organize multi-file changes for structured code reviews?▼

Organize multi-file changes by enforcing atomic commits with proper grouping based on concerns. This systematic change tracking approach creates a clean history that streamlines structured code reviews.

Related Skills

Explore More Software Engineering Skills→
SimHackerSimHacker
49

reward

Generates context-appropriate rewards for achievements, including items, abilities, titles, and heirlooms.

Community
Basic
vineet-codes256vineet-codes256

compose-and-push-commits

Organize staged and unstaged changes into atomic git commits and push them.

Community
Advanced
theslashdojotheslashdojo

git-rebase

Replay commits onto a new base with interactive rebase and autosquash.

Official
Intermediate
lugassawanlugassawan
2

principle-version-control

Guide Git version control with atomic commits and clear PR descriptions.

Community
Intermediate