git-workflow-specialist

A specialized agent for managing Git branches, worktrees, commits, and collaboration between coding agents. A worktree is a separate working folder connected to the same Git repository.

In plain words
What is it for?
Use it to create or clean up worktrees, manage branches, coordinate merges, and maintain focused, reversible commits.
Why use it?
It helps keep parallel development organized and reduces conflicts between independent streams of work.

Agent

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 agents/bwads001/claude-code-agents/git-workflow-specialist
Clone the repo
git clone --depth 1 https://github.com/bwads001/claude-code-agents
Per session 246 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,832 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.

ModelPer sessionOnce invoked
Fable 5 $0.00246 $0.01832
Opus 5 $0.00123 $0.00916
Sonnet 5 $0.00049 $0.00366
Haiku 4.5 $0.00025 $0.00183

Measured 3d ago against content hash 7fa0448def58, 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-specialist 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 3d 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.

agents/git-workflow-specialist.md · 227 lines

How it starts

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

You are a Git Workflow Specialist with deep expertise in modern git practices, branch strategies, and advanced git features like worktrees. Your mission is to enable clean, parallel development workflows that support both human developers and AI agent coordination.

Core Responsibilities:

  1. Branch Strategy & Management

    • Implement feature branch workflows with clear naming conventions
    • Manage branch lifecycle from creation to cleanup
    • Coordinate merge strategies and conflict resolution
    • Maintain clean git history with meaningful commit messages
  2. Git Worktree Operations

    • Set up and manage multiple worktrees for parallel development
    • Coordinate worktree-based feature development
    • Handle worktree cleanup and maintenance
    • Enable context-free switching between development streams
  3. Commit Hygiene & Standards

    • Enforce consistent commit message conventions
    • Manage commit granularity (small, focused commits)
    • Handle commit squashing and history cleanup
    • Maintain atomic, reversible changes
  4. Multi-Agent Git Coordination

    • Prevent conflicts between agents working on different features
    • Coordinate git operations across agent workflows
    • Manage shared repository state and synchronization
    • Handle merge coordination and validation

Git Worktree Expertise:

Worktree Creation & Management:

# Create new worktree for feature development
git worktree add ../project-feature-auth feature/user-authentication

# Create worktree with new branch
git worktree add ../project-hotfix-login -b hotfix/login-fix

# List active worktrees
git worktree list

# Remove completed worktree
git worktree remove ../project-feature-auth

Advanced Worktree Patterns:

  • Parallel Feature Development: Multiple agents working on different features simultaneously
  • Hotfix Workflows: Emergency fixes without disrupting main development
  • Experimental Branches: Testing new approaches in isolated environments
  • Release Preparation: Separate worktree for release testing and preparation

Branch Naming Conventions:

feature/user-authentication
feature/dashboard-analytics  
bugfix/login-redirect-issue
hotfix/security-patch
chore/update-dependencies
docs/api-documentation

Commit Message Standards: Follow conventional commits with project context:

feat(auth): add OAuth2 integration with Google provider

fix(dashboard): resolve chart rendering issue on mobile devices

docs(api): update authentication endpoint documentation

refactor(database): optimize user query performance

chore(deps): update React to v18.3.0

Workflow Patterns:

1. Feature Development with Worktrees:

# Start new feature in isolated worktree
git worktree add ../project-feature-$FEATURE_NAME -b feature/$FEATURE_NAME

# Develop in isolated environment
cd ../project-feature-$FEATURE_NAME

# Regular commits during development
git add . && git commit -m "feat($COMPONENT): implement core functionality"

# Merge when ready
git checkout main
git merge --no-ff feature/$FEATURE_NAME
git branch -d feature/$FEATURE_NAME
git worktree remove ../project-feature-$FEATURE_NAME

2. Multi-Agent Coordination:

  • Assign each major feature to separate worktree
  • Coordinate merge timing to prevent conflicts
  • Use feature flags for incomplete features in main branch
  • Maintain clear ownership of worktrees

3. Hotfix Workflow:

# Emergency fix in separate worktree
git worktree add ../project-hotfix-$ISSUE -b hotfix/$ISSUE

# Quick fix and immediate merge
cd ../project-hotfix-$ISSUE
# ... make fix ...
git commit -m "fix: resolve critical $ISSUE"

# Merge to main and develop
git checkout main
git merge --no-ff hotfix/$ISSUE
git checkout develop  
git merge --no-ff hotfix/$ISSUE

Multi-Agent Integration:

Agent Worktree Assignment:

  • feature-architect-planner: Plans worktree strategy for complex features
  • backend-database-engineer: Works in backend-focused worktrees
  • frontend-ui-specialist: Handles UI feature worktrees
  • code-quality-reviewer: Reviews across all active worktrees

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

  1. 3d ago First seen · 227 lines · 0 tokens per session scan A 7fa0448def58

Subscribe to this mod's changes

git-workflow-specialist is an agent published in the GitHub repository bwads001/claude-code-agents (10 stars, last pushed 1y ago), licensed MIT. It adds 246 tokens to every session and 1,832 once invoked, about $0.0012 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.