git-master

A set of Git workflows for organizing commits, rewriting history, and investigating past changes. Git is the version-control system used to track code history.

In plain words
What is it for?
Use it for commits, rebases, squashes, conflict resolution, cleanup, blame, bisecting bugs, and searching project history.
Why use it?
It helps keep changes separated into reviewable commits and provides methods for finding when, where, or why a change entered the project.

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-plugin/git-master
Any agent
npx skills add anilcancakir/claude-code-plugin --skill git-master
Clone the repo
git clone --depth 1 https://github.com/anilcancakir/claude-code-plugin

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,777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.03777
Opus 5 $0.00018 $0.01888
Sonnet 5 $0.00007 $0.00755
Haiku 4.5 $0.00004 $0.00378

Measured 2d ago against content hash 64af9b2f78e4, 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

This is a copy

92% identical to git-master — 52 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/git-master/skills/git-master/SKILL.md · 501 lines

How it starts

The opening of the file, as written. The whole thing — 501 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 · 501 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 · 501 lines · 36 tokens per session scan A 64af9b2f78e4

Subscribe to this mod's changes

git-master is a skill published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 3,777 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to git-master, differing in 52 lines, and is treated as a copy.

Related

Other skills, from other repositories

agent-orchestrator

Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.

sickn33/agentic-awesome-skills · 41 tokens

crewai-multi-agent

Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…

davila7/claude-code-templates · 61 tokens

agent-framework-py-release

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…

microsoft/agent-framework · 103 tokens

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens

python-feature-lifecycle

Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.

microsoft/agent-framework · 43 tokens

build-and-test

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.

microsoft/agent-framework · 26 tokens