git-workflows

git-workflows is a skill for Claude Code, Codex from miles990/claude-software-skills. It costs 14 tokens per session (2,531 once invoked), scanned A, original, MIT.

A guide to using Git, a tool that records code changes, with branching methods for working on features, releases, bug fixes, and team collaboration.

In plain words
What is it for?
Use it to choose a branching approach, create feature or release branches, prepare production fixes, and coordinate changes with collaborators.
Why use it?
It helps teams organize parallel work and reduce conflicts when several people change the same codebase.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is git worktree add ../project-hotfix hotfix/urgent-fix.

Good fit Use it to choose a branching approach, create feature or release branches, prepare production fixes, and coordinate changes with collaborators.

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/miles990/claude-software-skills
agentmods
npx agentmods add skills/miles990/claude-software-skills/git-workflows

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin git-workflows — /plugin install git-workflows after adding the marketplace above.

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-workflows

README.md
[![agentmods](https://agentmods.dev/badge/skills/miles990/claude-software-skills/git-workflows/github.svg)](https://agentmods.dev/skills/miles990/claude-software-skills/git-workflows)
Your own site
<a href="https://agentmods.dev/skills/miles990/claude-software-skills/git-workflows"><img src="https://agentmods.dev/badge/skills/miles990/claude-software-skills/git-workflows/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-workflows

Your own site · 80×15
<a href="https://agentmods.dev/skills/miles990/claude-software-skills/git-workflows"><img src="https://agentmods.dev/badge/skills/miles990/claude-software-skills/git-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,531 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.02531
Opus 5.5 $0.00006 $0.01012
Sonnet 5.5 $0.00003 $0.00506
Haiku 4.5 $0.00001 $0.00253

Measured 1mo ago against content hash ea4bab176662, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-workflows 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/setup-hooks.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

tools-integrations/git-workflows/SKILL.md · 472 lines

How it starts

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

Git Workflows

Overview

Git version control patterns, branching strategies, and team collaboration best practices.


Branching Strategies

Git Flow

main ─────●────────────●─────────────●───────────
           \          /               \
            \   release/1.0          release/1.1
             \    /    \              /
develop ──────●───●──────●────●──────●────────────
               \        /      \    /
            feature/   feature/ feature/
            login      payment  search
# Initialize git flow
git flow init

# Start a new feature
git flow feature start user-authentication
# Work on feature...
git flow feature finish user-authentication

# Start a release
git flow release start 1.0.0
# Bug fixes only...
git flow release finish 1.0.0

# Hotfix for production
git flow hotfix start critical-bug
git flow hotfix finish critical-bug

GitHub Flow (Simplified)

main ─────●──────●──────●──────●──────●───────
           \    /        \    /        \
         feature/       feature/      feature/
         add-auth       fix-bug       new-ui
# 1. Create branch from main
git checkout main
git pull origin main
git checkout -b feature/add-authentication

# 2. Make changes and commit
git add .
git commit -m "feat: add user authentication"

# 3. Push and create PR
git push -u origin feature/add-authentication
gh pr create --title "Add user authentication" --body "..."

# 4. After review, merge via GitHub
gh pr merge --squash

# 5. Delete branch
git checkout main
git pull origin main
git branch -d feature/add-authentication

Trunk-Based Development

main ────●──●──●──●──●──●──●──●──●────
         │     │        │
         └─────┴────────┴─── short-lived branches (< 1 day)
# Small, frequent commits directly to main or via short-lived branches
git checkout main
git pull
git checkout -b fix/typo-in-readme
# Make small change...
git commit -m "fix: typo in README"
git push -u origin fix/typo-in-readme
# PR, review, merge same day

Read the full file on GitHub · 472 lines

Files

What ships with it

6 files 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.

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 · 472 lines · 14 tokens per session scan A ea4bab176662

Subscribe to this mod's changes

git-workflows is a skill published in the GitHub repository miles990/claude-software-skills (26 stars, last pushed 9mo ago), licensed MIT. It adds 14 tokens to every session and 2,531 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-30.

Related

Other skills, from other repositories

git-docs

Git 2.49 — repositories, branching, merging, rebasing, remotes, submodules, hooks, internals, workflows.

pledgeandgrow/pledge-skills · 32 tokens

git-machete

Use whenever invoking the git machete CLI to organize branch chains, compute fork points, run stacked rebases/merges, or manage GitHub/GitLab PR/MR chains - especially in a repo that already has a .git/machete file. Lists which subcommands modify .git/machete, run rebase/merge, run hooks, or read stdin, so the agent…

VirtusLab/git-machete · 165 tokens

gitlab-merge-request-review

Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…

Knuckles-Team/gitlab-api · 158 tokens

next-issue

Work the next open item on the issue.

liatrio-labs/claude-code-gauntlet · 12 tokens

reissverschluss-merge

Reißverschluss-Verfahren (englisch: zipper merge) für sehr konfliktreiche Merges: Wenn zwei divergente Branches oder ein PR und sein Zielbranch BEIDE wertvolle, unvereinbar erscheinende Änderungen tragen, wird nicht pauschal eine Seite gewählt, sondern Abschnitt für Abschnitt verglichen, per Entscheidungstabelle…

ellmos-ai/skills · 189 tokens

github-pr-workflow

GitHub PR yaşam döngüsü — branch, commit, aç, CI izle, merge et.

furkangonel/cowrangler · 25 tokens