git-master

A Git-focused skill for recording changes, rewriting commit history, and investigating when or why code changed.

In plain words
What is it for?
It helps create atomic commits, rebase or squash work, resolve history problems, find the introduction of a change, and use Git investigation tools.
Why use it?
It provides a consistent way to handle commits, rebases, conflict resolution, blame, and searches through project history.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/anilcancakir/claude-code/git-master
Any agent
npx skills add anilcancakir/claude-code --skill git-master
Clone the repo
git clone --depth 1 https://github.com/anilcancakir/claude-code

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00036 $0.03809
Opus 5 $0.00018 $0.01904
Sonnet 5 $0.00007 $0.00762
Haiku 4.5 $0.00004 $0.00381

Measured 2d ago against content hash f77781d2c5cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-master scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/ac/skills/git-master/SKILL.md · 507 lines

How it starts

The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Master

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/who introduced specific changes

MODE DETECTION (FIRST STEP)

Analyze the user's request to determine operation mode:

User Request Pattern Mode Jump To
"commit", changes to commit, stage and commit COMMIT Phase 0-6
"rebase", "squash", "cleanup history", "fixup" REBASE Phase R1-R4
"find when", "who changed", "git blame", "bisect", "who wrote" HISTORY Phase H1-H3

Parse the actual request. Do not default to COMMIT mode.


CORE PRINCIPLE: MULTIPLE COMMITS BY DEFAULT

ONE COMMIT FROM MANY FILES = FAILURE

Default behavior is to CREATE MULTIPLE COMMITS. Single commit from multiple files is a bug in your logic.

Hard rule:

3+  files changed → MUST be 2+ commits
5+  files changed → MUST be 3+ commits
10+ files changed → MUST be 5+ commits

If about to make 1 commit from multiple files - STOP AND SPLIT.

Split criteria:

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 true:

  • Exact same atomic unit (e.g., function + its test)
  • Splitting would break compilation
  • One-sentence justification exists

COMMIT MODE (Phase 0-6)

Phase 0: Parallel Context Gathering

Execute ALL commands in parallel:

# Group 1: Current state
git status
git diff --staged --stat
git diff --stat

# Group 2: History context
git log -30 --oneline
git log -30 --pretty=format:"%s"

# Group 3: Branch context
git branch --show-current
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM"
git log --oneline $(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null)..HEAD 2>/dev/null

Read the full file on GitHub · 507 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 507 lines · 36 tokens per session scan A f77781d2c5cf

Subscribe to this mod's changes

git-master is a skill published in the GitHub repository anilcancakir/claude-code (3 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 3,809 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens