git-master

git-master is a skill for Claude Code, Codex from znlgis/my-opencode-deepseek-config. It costs 75 tokens per session (1,294 once invoked), scanned A, original, MIT.

A guide to advanced Git operations, where Git is a tool for tracking changes to code. It covers history editing, finding when code changed, recovering lost work, comparing revisions, and managing isolated workspaces.

In plain words
What is it for?
Use it for rebasing, squashing commits, fixing up history, blame or code archaeology, bisecting bugs, reflog recovery, cherry-picking, and worktrees.
Why use it?
It provides safe procedures for complex repository maintenance that basic Git commands do not cover. It also emphasizes reviewing changes and avoiding unsafe history rewrites.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is git worktree add ../feature-x feature-branch # checkout a branch in a separate dir.

Good fit Use it for rebasing, squashing commits, fixing up history, blame or code archaeology, bisecting bugs, reflog recovery, cherry-picking, and worktrees.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-config
agentmods
npx agentmods add skills/znlgis/my-opencode-deepseek-config/git-master

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for git-master

README.md
[![agentmods](https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/git-master/github.svg)](https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/git-master)
Your own site
<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/git-master"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/git-master/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for git-master

Your own site · 80×15
<a href="https://agentmods.dev/skills/znlgis/my-opencode-deepseek-config/git-master"><img src="https://agentmods.dev/badge/skills/znlgis/my-opencode-deepseek-config/git-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,294 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Tool Misuse · line 140
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
How audits are shown
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.1 $0.00075 $0.01294
Opus 5.5 $0.00030 $0.00518
Sonnet 5.5 $0.00015 $0.00259
Haiku 4.5 $0.00007 $0.00129

Measured 1mo ago against content hash 7a2061f1a0cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

opencode/skills/git-master/SKILL.md · 149 lines

How it starts

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

Git Master

Advanced Git patterns for when the basics aren't enough.

When to use me

  • Rebasing, squashing, or interactive history editing
  • Finding when/where code was introduced or deleted (git blame, git log -S/-G)
  • Recovering lost commits or branches (git reflog)
  • Bisecting to find the commit that introduced a bug
  • Cherry-picking or fixup workflows
  • Managing stacked branches or worktrees

Atomic commits

One logical change per commit. Before committing, review with:

git add -p              # stage hunks interactively — only what belongs together
git diff --cached       # review exactly what you're about to commit

If the diff mixes unrelated changes, split them into separate commits.

Rewriting history (safety first)

Never rewrite shared/pushed history unless you own the branch and no one else works on it. For personal branches:

# Interactive rebase — reorder, squash, or edit commits
git rebase -i HEAD~5     # last 5 commits
git rebase -i main        # rebase onto main interactively

# Squash the last N commits into one
git reset --soft HEAD~3   # uncommit last 3, keep changes staged
git commit -m "feat: combined feature work"

# Fixup — amend a past commit without a separate "fix" commit
git commit --fixup <sha>  # mark this as a fix for <sha>
git rebase -i --autosquash main  # automatically reorder+squash fixups

# Amend the last commit (not pushed yet)
git commit --amend --no-edit    # add staged changes to last commit
git commit --amend -m "better message"

Code archaeology

Find when code was introduced, changed, or deleted:

# Who last touched each line?
git blame path/to/file -L 40,60    # blame lines 40-60

# When was this string added/removed? (-S = pickaxe)
git log -S "functionName" --oneline -- path/
git log -S "removed_feature" --patch       # show the diff that removed it

# When was a regex pattern changed? (-G = grep-based)
git log -G "TODO|FIXME" --oneline

# Find which commit deleted a file
git log --all --full-history -- "**/deleted-file.ts"

# Show a file at a specific point in time
git show <commit>:path/to/file.ts
git show <commit>~1:path/to/file.ts   # the version before that commit

Read the full file on GitHub · 149 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. 1mo ago First seen · 149 lines · 75 tokens per session scan A 7a2061f1a0cd

Subscribe to this mod's changes

git-master is a skill published in the GitHub repository znlgis/my-opencode-deepseek-config (59 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,294 once invoked, about $0.0003 per session on Opus 5.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-30.

Related

Other skills, from other repositories

git-workflow

Branching strategies, conventional commits, PR templates, and merge vs rebase guidance. Activate when starting features, creating PRs, or managing releases.

DVNghiem/FlowDeck · 34 tokens

smart-git-commit

Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…

Zarl-prog/Smart-git-commit · 148 tokens

commit-pr

A command for the workflow of committing code, sending it to a remote Git repository, and opening or updating a pull request. A pull request is a proposed change for review and merging.

gitgitWi/council-flow · 139 tokens

git

Unified git workflow for branch-first development: status/diff review, security-first commits, worktrees, and PR creation/review via gh. Auto-activates on: "commit", "push", "branch", "worktree", "pr", "pull request", "merge", "rebase", "git".

bntvllnt/agent-skills · 66 tokens

update-v8-version

Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.

openinterpreter/openinterpreter · 86 tokens

changelog

Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.

Donchitos/Claude-Code-Game-Studios · 22 tokens