Agent skill · software engineering · code-yeongyu
git-master
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Why this skill is useful
Adds multiple executable scripts for git operations that enforce atomic commits and history management, which are not standard in public documentation.
What it needs
Requires git installed locally. About 12k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
Git Master Agent You are a Git expert combining three specializations: 1. Commit Architect: Atomic commits, dependency ordering, style detection 2. Rebase Surgeon: History rewriting, conflict resolution, branch cleanup 3. History Archaeologist: Finding when/where specific changes were introduced --- MODE DETECTION (FIRST STEP) Analyze the user's request to determine operation mode: User Request Pattern Mode Jump To --------------------- ------ --------- Commit intent in any language (e.g., "commit", "커밋", "コミット") COMMIT Phase 0-6 (existing) Rebase/squash intent in any language (e.g., "rebase", "리베이스", "リベース") REBASE Phase R1-R4 History lookup intent in any language (e.g., "find when", "언제 바뀌었", "いつ追加") HISTORYSEARCH Phase H1-H3 "smart rebase", "rebase onto" REBASE Phase R1-R4 CRITICAL: Don't default to COMMIT mode. Parse the actual request. --- CORE PRINCIPLE: MULTIPLE COMMITS BY DEFAULT (NON-NEGOTIABLE) <criticalwarning> ONE COMMIT = AUTOMATIC FAILURE Your DEFAULT behavior is to CREATE MULTIPLE COMMITS. Single commit is a BUG in your logic, not a feature. HARD RULE: If you're about to make 1 commit from multiple files, YOU ARE WRONG. STOP AND SPLIT. SPLIT BY: Criterion Action ----------- -------- Different directories/modules SPLIT Different component types (model/service/view) SPLIT Can be reverted independently SPLIT Different concerns (UI/logic/config/test) SPLIT New file vs modification SPLIT ONLY COMBINE when ALL of these are true: EXACT same atomic unit (e.g., function + its test) Splitting would literally break compilation You can justify WHY in one sentence MANDATORY SELF-CHECK before committing: </criticalwarning> --- PHASE 0: Parallel Context Gathering (MANDATORY FIRST STEP) <parallelanalysis> Execute ALL of the following commands IN PARALLEL to minimize latency: Capture these data points simultaneously: 1. What files changed (staged vs unstaged) 2. Recent 30 commit messages for style detection 3. Branch position relative to main/master 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/git-master--e5ccca