A shared set of rules for common Git work, including commits, branches, pushes, merges, rebases, and pull requests. Git is the version-control system used to record and combine code changes.

Use it when committing code, creating or merging branches, pushing changes, preparing pull requests, rebasing, or force-pushing when explicitly required.

It gives agents a consistent way to save, organize, share, and review changes in a repository, including rules for when to create branches and how to label commits.

git-flow — Skill for Claude Code by Xakki

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 Xakki/ai-agents-skills --skill git-flow

Clone the repo

git clone --depth 1 https://github.com/Xakki/ai-agents-skills

Made for: Claude Code.

Or install ai-agents-skills, the plugin that ships this one along with the rest of its 23 skills, 3 agents, 6 hooks.

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/xakki/ai-agents-skills/git-flow.svg)](https://agentmods.dev/skills/xakki/ai-agents-skills/git-flow)

Your own site

<a href="https://agentmods.dev/skills/xakki/ai-agents-skills/git-flow"><img src="https://agentmods.dev/badge/skills/xakki/ai-agents-skills/git-flow.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 985 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.00099	$0.00985
Opus 5	$0.00049	$0.00492
Sonnet 5	$0.00020	$0.00197
Haiku 4.5	$0.00010	$0.00098

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

Security

Grade A, and why

git-flow 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 7d 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.

skills/git-flow/SKILL.md · 55 lines

How it starts

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

git-flow — shared git core

Single source of truth for how agents do git in this plugin. Other git-using skills (kanban, schedule-tasks, prepare-pr, qa-check, git-move) follow this CORE and document only their own context-specific deltas. Edge cases and longer examples → reference.md.

CORE rules

Default = commit to the default branch. An agent commits its work directly to the default branch; the user reviews via commit history. Create a feature/·fix/·chore/ branch only when the user explicitly asks, OR when another skill defines its own branch model (kanban does — per-task task/<ID> branch; schedule-tasks runs an autonomous branch+park model).
Branch naming (when branches are used): feature/<short>, fix/<short>, chore/<short>.
Who commits. Each sub-agent / teammate commits its OWN zone's changes when it finishes that zone. End every commit message with a footer line naming the zone: Agent: <zone> (e.g. Agent: backend). This Agent: <zone> marker is the ONLY allowed trailer — do NOT add Co-Authored-By:, Generated with …, or any other signature. Prompt and execution evidence belongs in Kanban records, never extra Git trailers.
Commit message format. <scope>: <imperative summary>. Subject ≤72 chars, imperative mood. Body optional (may be in Russian) — include it only when it adds meaning not visible from the diff. Keep the whole message readable.
Scopes (generic default set): api | db | infra | docs | task. Projects extend/override this list in their own CLAUDE.md (e.g. a Go-client project may add goclient; a browser-extension project may add ext). Do NOT treat project-specific scopes as the canonical set.
Staging — explicit paths only. git add <path> …. Never git add ., git add -A, git add -u, or git commit -a. (Resume-context exception → schedule-tasks documents it.)
Never force-push to the default branch. Never git commit --no-verify.
Moving / renaming / deleting tracked files → use the git-move skill (git mv / git rm). Do not duplicate its mechanics.
PR. Title in English; body may be in Russian.

Read the full file on GitHub · 55 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

reference.md 2.1 KB

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.

7d ago First seen · 55 lines · 99 tokens per session scan A c2c904eca003

Subscribe to this mod's changes

git-flow is a skill published in the GitHub repository Xakki/ai-agents-skills (6 stars, last pushed 16d ago), licensed MIT. It adds 99 tokens to every session and 985 once invoked, about $0.0005 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.

Claude Code Commits Git and workflow agentic-workflow ai-agents automation developer-tools kanban

security-pipeline

Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.

sangrokjung/claude-forge · 48 tokens

github-commenting

How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.

juspay/neurolink · 41 tokens

git-pushing

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

mhattingpete/claude-skills-marketplace · 70 tokens

git-flow