What is git-workflow?

A Git workflow guide based on branches, pull requests, and release branches. A pull request is a proposed change reviewed before it is merged.

Use it to create feature branches, open pull requests, resolve merge conflicts, manage stashes, and tag releases.

It prevents direct changes to the main branch and provides a fixed process for starting work, reviewing changes, and publishing releases.

git-workflow — Skill for Claude Code and Codex by RealDougEubanks: A Git workflow guide based on branches, pull requests…

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.

agentmods

npx agentmods add skills/realdougeubanks/claudemarketplace/git-workflow

Any agent

npx skills add RealDougEubanks/ClaudeMarketplace --skill git-workflow

Clone the repo

git clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplace

Made for: Claude Code, Codex.

Or install git-workflow, the plugin that ships this one along with the rest of its 1 skill.

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/realdougeubanks/claudemarketplace/git-workflow.svg)](https://agentmods.dev/skills/realdougeubanks/claudemarketplace/git-workflow)

Your own site

<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/git-workflow"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/git-workflow.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 2,864 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00034	$0.02864
Opus 5	$0.00017	$0.01432
Sonnet 5	$0.00007	$0.00573
Haiku 4.5	$0.00003	$0.00286

Measured 5d ago against content hash 2ecd1c3c4838, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-workflow 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 5d 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-workflow/SKILL.md · 299 lines

How it starts

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

Git Workflow — Release-Branch Model

Enforce the release-branch Git model and help execute the correct git operations for your current context: start new work, open a PR, cut a release, or view the workflow reference.

Hard Rules (always enforced, no exceptions)

Never commit or push directly to main. If the current branch is main, stop and create a new branch before making any changes.
Never force-push to main.
All changes must reach main via a PR from a release branch.

Instructions

When invoked, ask the user what they want to do (if not already specified):

"What would you like to do? (a) View the Git workflow reference (b) Start new work — scaffold a feature or fix branch (c) Open a PR for the current branch (d) Cut a release — merge release branch to main and tag (e) Resolve a merge conflict on the current branch (f) Manage stashes — list, view, apply, or drop stashes"

Then execute the appropriate action below.

Action (a) — View Workflow Reference

Print the full Git Workflow Reference section below.

Action (b) — Start New Work

Use Bash to identify the current release branch:
```
git branch -r | grep release | sort -V | tail -1
```
No-release-branch fallback: If the command above returns no output (no release/* branch exists), fall back to branching from main and target main for the PR. Inform the user:

"No release branch found. Branching from main and the PR will target main directly. This is normal for simple repos and early-stage projects that do not yet use the release-branch model." In this case, replace origin/<release-branch> in step 4 with origin/main, and use --base main in the gh pr create call in Action (c).
Ask the user:
- Is this a new feature or a bug fix? (determines feature/ vs fix/ prefix)
- What is the task ID or short description? (e.g. task-042, login-crash)
Construct the branch name: feature/task-XXX-short-description or fix/task-XXX-short-description.

Read the full file on GitHub · 299 lines

Files

What ships with it

4 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.

5d ago First seen · 299 lines · 34 tokens per session scan A 2ecd1c3c4838

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 2,864 once invoked, about $0.0002 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 Releases claude claude-ai claude-code claude-code-plugin claude-code-skill claude-code-skills

release-notes

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

foyzulkarim/skills · 51 tokens

release-checklist

Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.

IdoCohen560/claude-unity-game-studio · 26 tokens

changelog

Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.

IdoCohen560/claude-unity-game-studio · 29 tokens

swarm

Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…

Zintellix/Claude-Skills · 138 tokens

tools-unity-behavior-designer

Behavior Designer patterns for AI behavior trees including task creation, shared variables, conditionals, and debugging.