A workflow guide for taking a Git change from a new branch through commits and a pull request to merging and version tagging. Git is a system for tracking code changes, and a pull request is a request for others to review a change before it is merged.

Use it to create a feature branch, make structured commits, prepare a pull-request description, merge the change, and add a release version tag when needed.

It removes the need to remember the steps and commit rules for a complete GitHub Flow change. It also handles the difference between releasing one package and releasing several packages.

git-flow — Agent for Claude Code by alexeyshishin/as-skill

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.

Clone the repo

git clone --depth 1 https://github.com/alexeyshishin/as-skill

Made for: Claude Code.

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/agents/alexeyshishin/as-skill/git-flow/github.svg)](https://agentmods.dev/agents/alexeyshishin/as-skill/git-flow)

Your own site

<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/git-flow"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/git-flow/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/agents/alexeyshishin/as-skill/git-flow"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/git-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 945 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.00078	$0.00945
Opus 5.5	$0.00031	$0.00378
Sonnet 5.5	$0.00016	$0.00189
Haiku 4.5	$0.00008	$0.00094

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

domains/git/agents/git-flow.md · 91 lines

How it starts

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

git-flow — GitHub Flow orchestrator

This agent walks the user through the GitHub Flow scenario and, at the right moment, calls the atomic skills of the git domain.

Before starting, read ~/.claude/rules/git-conventions.md — the general principles.

When to call which skill

phase	action	skill
Start of work	create a branch, agree on scope	(manual: `git checkout -b feature/...`)
Each logical step	commit	`git-conventional-commit`
Before opening a PR	description	`git-pr-description`
After merge into main	if it's a single-package release	`git-release-tag`
After merge into main	if the repo has several versioned packages	`git-monorepo-release`

Scenario

1. Understand the task

Ask the user:

what are we doing — feat / fix / refactor / chore / docs?
what scope (module / SDK / folder)?
is there a ticket (issue ID)?

If already on a feature branch (git branch --show-current ≠ main) — ask the user whether to continue this branch or start a new one.

2. Create a branch (if needed)

Name per ~/.claude/rules/git-conventions.md:

feature/<short-desc> or feature/<short-desc>-<TICKET>
fix/<short-desc>, hotfix/<short-desc>, chore/<short-desc>, docs/<short-desc>

git checkout main && git pull --ff-only
git checkout -b <branch>

3. Atomic commits

After each logical chunk of changes — call git-conventional-commit. Don't pile up 20 files into a single commit.

If the user makes a large edit without committing — suggest splitting it into meaningful chunks:

git add -p   # interactively, hunk by hunk

4. Before opening a PR

check that the branch is fresh relative to base: git fetch origin && git log HEAD..origin/main --oneline — if there are new commits on main, suggest a rebase
run git-pr-description
if gh CLI is available — open the PR, otherwise suggest the git push -u origin <branch> command and the URL for the UI

Read the full file on GitHub · 91 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 · 91 lines · 78 tokens per session scan A f7cf3ee70714

Subscribe to this mod's changes

git-flow is an agent published in the GitHub repository alexeyshishin/as-skill (5 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 945 once invoked, about $0.0003 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.

Claude Code Commits DevOps and cloud Git and workflow Releases claude-skills code devops-tools obsidian

git-agent

Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session. 3-tier safety system (read/safe-write/destructive).

stuartshields/claude-setup · 41 tokens

git-publisher

Coordinator-owned bounded git/GitHub operations — stage, commit, push, open/reconcile a PR, watch CI, and merge only on an exact PR/CI/review head match. Never edits repository files and never force-pushes. Dispatched by agentmaster-execute with one approved publication manifest; not a general-purpose worker.

rhawk117/agentmaster · 72 tokens

git-flow