git-workflow

git-workflow is a skill for Claude Code, Codex from jezweb/claude-skills. It costs 52 tokens per session (1,037 once invoked), scanned A, original, MIT.

A set of guided procedures for Git, the version-control system used to track code changes. It covers pull requests, branch cleanup, merge conflicts, release tags, and squashing commits.

In plain words
What is it for?
Use it to prepare a pull request, remove merged branches, resolve conflicts, manage monorepo tags, or follow a squash-and-merge process.
Why use it?
It gives you a clear sequence of checks and commands for Git tasks that are easy to get wrong. It uses commit history and repository status to help prepare accurate pull requests.

Skill for Claude CodeCodex

Part of the dev-tools plugin — 16 skills, 14 commands shipped together

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/jezweb/claude-skills/git-workflow
Any agent
npx skills add jezweb/claude-skills --skill git-workflow
Clone the repo
git clone --depth 1 https://github.com/jezweb/claude-skills

Made for: Claude Code, Codex.

Or install dev-tools, the plugin that ships this one along with the rest of its 16 skills, 14 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/jezweb/claude-skills/git-workflow.svg)](https://agentmods.dev/skills/jezweb/claude-skills/git-workflow)
Your own site
<a href="https://agentmods.dev/skills/jezweb/claude-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/git-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,037 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.00052 $0.01037
Opus 5 $0.00026 $0.00518
Sonnet 5 $0.00010 $0.00207
Haiku 4.5 $0.00005 $0.00104

Measured 5d ago against content hash cfe9c9601e73, 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.

plugins/dev-tools/skills/git-workflow/SKILL.md · 153 lines

How it starts

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

Git Workflow

Guided workflows for common git operations that benefit from structured steps.

PR Preparation

When preparing a pull request:

  1. Gather context

    • git log main..HEAD --oneline — list all commits on the branch
    • git diff main...HEAD --stat — see all changed files
    • git status — check for uncommitted work
  2. Draft PR content

    • Title: under 70 chars, describes the change (not the branch name)
    • Body: summarise the "why", list key changes, add test plan
    • Use the commit history to write the summary — don't rely on memory
  3. Push and create

    git push -u origin HEAD
    gh pr create --title "..." --body "$(cat <<'EOF'
    ## Summary
    - ...
    
    ## Test plan
    - [ ] ...
    
    🤖 Generated with [Claude Code](https://claude.com/claude-code)
    EOF
    )"
    
  4. Verifygh pr view --web to open in browser

Branch Cleanup

Clean up merged branches safely:

  1. Switch to main and pull latest

    git checkout main && git pull
    
  2. List merged branches (excludes main/master/develop)

    git branch --merged main | grep -vE '^\*|main|master|develop'
    
  3. Delete local merged branches

    git branch --merged main | grep -vE '^\*|main|master|develop' | xargs -r git branch -d
    
  4. Prune remote tracking refs

    git fetch --prune
    
  5. List remote branches with no local tracking (optional)

    git branch -r --merged origin/main | grep -vE 'main|master|develop|HEAD'
    

Merge Conflict Resolution

When a PR has conflicts:

  1. Assess the conflict scope

    git fetch origin
    git merge origin/main --no-commit --no-ff
    git diff --name-only --diff-filter=U  # List conflicted files
    
  2. For each conflicted file, read the file and resolve:

    • Keep both changes if they're in different areas
    • If architecturally incompatible, prefer the main branch's approach and re-apply the PR's intent on top

Read the full file on GitHub · 153 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. 5d ago First seen · 153 lines · 52 tokens per session scan A cfe9c9601e73

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository jezweb/claude-skills (993 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,037 once invoked, about $0.0003 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-30.