What is git-workflow?

A guide to organising Git work with branches, commits, and pull requests. Git records code changes, while a branch is a separate line of work and a pull request is a review request for merging it.

Use it to name branches, write Conventional Commits, prepare feature or bug-fix changes, and manage pull-request workflows.

It makes code history easier to understand and gives teams consistent names and messages for reviewing and merging changes.

git-workflow — Skill for Claude Code and Codex by furkangonel

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 furkangonel/cowrangler --skill git-workflow

Clone the repo

git clone --depth 1 https://github.com/furkangonel/cowrangler

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

Your own site

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

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

When invoked 742 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.00016	$0.00742
Opus 5.5	$0.00006	$0.00297
Sonnet 5.5	$0.00003	$0.00148
Haiku 4.5	$0.00002	$0.00074

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

bundled_skills/git-workflow/SKILL.md · 118 lines

How it starts

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

Git Workflow SOP

Branch Naming Convention

feature/<ticket>-short-description    # New features
fix/<ticket>-short-description        # Bug fixes  
chore/<ticket>-short-description      # Maintenance, deps, tooling
docs/<ticket>-short-description       # Documentation only
refactor/<ticket>-short-description   # Code restructuring
hotfix/<ticket>-short-description     # Urgent production fixes

Conventional Commits Format

<type>(<scope>): <short description>

[optional body — explain WHY, not what]

[optional footer — BREAKING CHANGE: ..., Closes #123]

Types

Type	When to use
`feat`	New user-visible feature
`fix`	Bug fix
`chore`	Build system, tooling, dependencies
`docs`	Documentation changes only
`refactor`	Code change that doesn't fix a bug or add a feature
`test`	Adding or fixing tests
`perf`	Performance improvement
`ci`	CI/CD pipeline changes
`revert`	Reverts a previous commit

Good commit message examples

feat(auth): add OAuth2 Google login support

fix(api): handle null response from payment gateway

Closes #892. The gateway returns null instead of an error object
when the card is declined — we now normalize this to a proper error.

chore: upgrade typescript to 5.4 and fix type errors

BREAKING CHANGE: strict null checks now enforced everywhere

Standard Workflow

# 1. Start from fresh main
git checkout main && git pull

# 2. Create feature branch  
git checkout -b feature/123-add-user-avatar

# 3. Make focused commits as you work
git add -p                          # Stage only what belongs to this commit
git commit -m "feat(users): add avatar upload endpoint"

# 4. Keep branch current with main
git fetch origin && git rebase origin/main

# 5. Before PR: squash if needed
git rebase -i origin/main

# 6. Push and open PR
git push -u origin HEAD

PR Description Template

## What
Brief description of what this PR does.

## Why
Why is this change needed? Link to issue/ticket.

## How
Key implementation decisions made and why.

## Testing
How was this tested? What should reviewers verify?

## Screenshots (if UI change)

## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No console.log / debug code left
- [ ] Breaking changes documented

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

2mo ago First seen · 118 lines · 16 tokens per session scan A 25374ecbde22

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository furkangonel/cowrangler (1 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 742 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.

Git and workflow agent agent-skills agent-tools ai cli cli-agent

git-workflow