A guide to using Git, the version-control system used to track code changes. It covers branches, commits, pull requests, worktrees, merge conflicts, and standard commit messages.

Use it when creating branches, writing commits, preparing pull requests, managing parallel work, resolving conflicts, or reorganizing Git history.

It helps keep changes organized and makes the project history easier to understand, review, merge, and use for automated release notes.

git-expert — Skill for Claude Code and Codex by ApexIQ/skillsmith

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.

Any agent

npx skills add ApexIQ/skillsmith --skill git_expert

Clone the repo

git clone --depth 1 https://github.com/ApexIQ/skillsmith

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/apexiq/skillsmith/git_expert/github.svg)](https://agentmods.dev/skills/apexiq/skillsmith/git_expert)

Your own site

<a href="https://agentmods.dev/skills/apexiq/skillsmith/git_expert"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/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/skills/apexiq/skillsmith/git_expert"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/git_expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 819 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.00031	$0.00819
Opus 5.5	$0.00012	$0.00328
Sonnet 5.5	$0.00006	$0.00164
Haiku 4.5	$0.00003	$0.00082

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

.agent/skills/git_expert/SKILL.md · 92 lines

How it starts

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

🌿 Git Expert — Production-Grade Source Control

Philosophy: Git history is a technical document, not a personal diary. Every commit should be a discrete, atomic improvement with a clear record of "why" and "what."

1. When to Use This Skill

Creating new branches or managing worktrees
Writing commit messages (Conventional Commits)
Preparing Pull Requests or structured diffs
Navigating complex git history (rebase, squash, cherry-pick)
Resolving merge conflicts
Organizing parallel development streams

2. Conventional Commits (Automation-Ready)

Always use the Conventional Commits specification for automated changelogs and versioning.

Structure

<type>[optional scope]: <description>

Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
chore: Changes to the build process or auxiliary tools and libraries

Example

feat(auth): add OIDC provider support for team-service
fix(ui): resolve clipping issue on mobile headers
docs: update competitive audit findings in README

3. Worktree Management (Context Switching)

Use git worktree to work on multiple branches simultaneously without affecting your main working directory. This is critical for high-velocity teams.

Workflow

Create: git worktree add ../feature-branch feature-branch
List: git worktree list
Remove: git worktree remove ../feature-branch

Rule: Always keep worktrees outside the main project folder to avoid nested repository confusion.

4. Branching Strategy

Branch	Purpose
`main`	Production-ready, stable code.
`develop`	Integration branch for features.
`feat/*`	Feature-specific development.
`fix/*`	Bug fixes for existing features.
`hotfix/*`	Critical production fixes.

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

1mo ago First seen · 92 lines · 31 tokens per session scan A f6d365686eef

Subscribe to this mod's changes

git-expert is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 819 once invoked, about $0.0001 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-31.

Commits Git and workflow Releases agentic-ai ai-agents ai-coding-assistant ai-developer-tools autonomous-repair cli-tool context-management promoted

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

git-integration

Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.

a5c-ai/babysitter · 39 tokens

git-workflow

Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…

ericrisco/rsc-harness · 127 tokens

document

Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.

jsmastery-pro/skills · 65 tokens

kirocrew-prepare-pr

LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.

kirodotdev/KiroCrew · 85 tokens

ship-change

Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…

BlackBeltTechnology/pi-agent-dashboard · 129 tokens