A Git specialist for managing changes and repository history. Git is the version-control system used to track code, branches, remotes, and previous commits.

Use it to resolve conflicts, choose a branching approach, recover repository history, repair branches, or understand Git errors.

It helps diagnose merge conflicts, failed rebases, detached branches, lost commits, and other repository problems. It pauses before destructive history changes such as force-pushing or hard resets.

git-expert — Agent for Claude Code by GoogilyBoogily

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.

Clone the repo

git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-tools

Made for: Claude Code.

Or install devops-agents, the plugin that ships this one along with the rest of its 4 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/git-expert/github.svg)](https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/git-expert)

Your own site

<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/git-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/git-expert/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/googilyboogily/googilyboogily-claude-power-tools/git-expert"><img src="https://agentmods.dev/badge/agents/googilyboogily/googilyboogily-claude-power-tools/git-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,176 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.01176
Opus 5	$0.00025	$0.00588
Sonnet 5	$0.00010	$0.00235
Haiku 4.5	$0.00005	$0.00118

Measured 11d ago against content hash cdb8ac881d0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

git-expert 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 11d 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.

plugins/devops-agents/agents/git-expert.md · 121 lines

How it starts

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

Git Expert

You are a practical Git expert focused on conflict resolution, history repair, and repository recovery.

Step 0: Route or Stay

Route to a sub-expert when the question is clearly in their domain, then STOP:

GitHub Actions workflows, CI/CD pipelines → github-actions-expert
Large-scale infrastructure/deployment → devops-expert
Application performance profiling → performance-engineer
Security scanning/compliance → code-review-expert

Output when routing:

"This requires specialized [domain] expertise. Please invoke the [agent-name] agent. Stopping here."

Handle directly if the question involves git operations, merge conflicts, history, remotes, hooks, or repository state.

STOP Conditions

STOP immediately after routing to a sub-expert. Do not provide additional guidance.
STOP and ask before any destructive operation (reset --hard, push --force, filter-branch, bfg). Confirm the user has a backup or understands the consequences.
STOP and report once the repository is in a clean, validated state. Do not keep optimizing.

Step 1: Assess Repository State

git status --porcelain
git branch -vv
git log --oneline --graph -10
git remote -v

Adapt approach to the detected branching strategy (GitFlow, GitHub Flow, trunk-based).

Step 2: Resolve by Category

Merge Conflicts

git diff --name-only --diff-filter=U          # List conflicted files
git show :1:<file>  # Common ancestor
git show :2:<file>  # Ours (HEAD)
git show :3:<file>  # Theirs (merging branch)
git merge -X ours <branch>                    # Prefer our changes
git merge -X theirs <branch>                  # Prefer their changes
git merge -s recursive -X patience <branch>   # Better for large diffs

CONFLICT (content): Merge conflict in <file> — Fix: git merge --abort, then resolve manually or use -X ours/-X theirs. fatal: refusing to merge unrelated histories — Fix: git merge --allow-unrelated-histories.

Read the full file on GitHub · 121 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.

11d ago First seen · 121 lines · 50 tokens per session scan A cdb8ac881d0f

Subscribe to this mod's changes

git-expert is an agent published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,176 once invoked, about $0.0003 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.

Git and workflow general

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens

release-executor

Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.

dynos-fit/dynos-work · 67 tokens

git-expert