skills.rest
Lee-SiHyeon
Lee-SiHyeonCOMMUNITY
Explore all skills by this author →
GitHub

git-master

Plans and executes safe Git operations from natural-language requests.

10|Updated Mar 22, 2026
Search Tags:#git#commit#rebase#bisect#blame#history search#atomic changes
One-click install
npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill git-master-lee-sihyeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-master
Source: https://github.com/Lee-SiHyeon/oh-my-copilot/tree/main/.github/skills/git-master
Command: npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill git-master-lee-sihyeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy Git history by guiding you to produce correctly structured commits, safe rebases, and accurate historical explanations when you change code.

Core Features & Use Cases

  • Atomic commit planning for staged work: Splits changes into 2+ commits when multiple files are involved and enforces a minimum commit count, then verifies staging and outputs commit messages in the detected language and style.
  • History rewriting with guardrails: Performs interactive rebase with autosquash, avoids force-pushing to main/master, and provides a rebuild strategy for messy local history.
  • History archaeology for accountability: Uses blame, search-based history, and bisect to answer who changed what, when it happened, and where a behavior/bug was introduced.

Quick Start

Tell the AI: “Use git-master to commit my current staged changes with atomic multi-commit planning and verify the final working tree is clean.”

Frequently Asked Questions about git-master

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

FAQPage Schema
How do I split staged changes into multiple atomic commits?▼

To create atomic commits, this Skill plans multi-file staged work into two or more commits by detecting your style, verifying staging, and generating commit messages in your language to keep your Git history clean.

What is the safest way to clean up messy local Git history?▼

Cleaning local Git history safely requires interactive rebase with autosquash. This Skill performs history rewriting with guardrails, providing a rebuild strategy while avoiding force-push to main or master branches.

How does git bisect help find when a bug was introduced?▼

Git bisect finds when a bug was introduced by systematically checking commits. This Skill uses bisect alongside blame and search-based history to answer who changed what, when it happened, and where a behavior started.

Can I use natural language to search Git history and run rebases?▼

Yes, you can use natural language to search Git history and run rebases. This Skill turns plain requests into COMMIT, REBASE, or HISTORY_SEARCH workflows by enforcing mode detection from your input.

What are the limitations when rewriting Git history with interactive rebase?▼

A key limitation of rewriting Git history is avoiding force-push to main or master. This Skill enforces safety constraints to prevent destructive updates to protected branches during interactive rebase with autosquash.

Related Skills

Explore More Software Engineering Skills→
saadjssaadjs

git-incremental-commits

Convert uncommitted changes into small conventional commits via git add -p.

Community
Advanced
vineet-codes256vineet-codes256

compose-and-push-commits

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

Community
Advanced
gabrielfruetgabrielfruet
3

git-workflow

Stage, commit, and push Git changes with diff review and rebase recovery.

Community
Advanced
gewoonsebagewoonseba
9

rebase-main

Rebase the current branch onto origin/main after conflict resolution.

Community
Advanced