git-workflow

A guided assistant for common Git tasks, including branches, commits, pull requests, merge conflicts, and keeping project history tidy. Git is a system for tracking changes to code.

In plain words
What is it for?
Use it for branching decisions, conventional commit messages, opening pull requests, resolving merge conflicts, or getting help with Git.
Why use it?
It provides a structured path through Git operations that can otherwise be easy to perform incorrectly or inconsistently.

Skill for Claude CodeCodex

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/dvasyliev/ai-dev-tools-getting-started/git-workflow
Any agent
npx skills add dvasyliev/ai-dev-tools-getting-started --skill git-workflow
Clone the repo
git clone --depth 1 https://github.com/dvasyliev/ai-dev-tools-getting-started

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 920 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00060 $0.00920
Opus 5 $0.00030 $0.00460
Sonnet 5 $0.00012 $0.00184
Haiku 4.5 $0.00006 $0.00092

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

claude-code/skills/git-workflow/SKILL.md · 142 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 142 lines · 60 tokens per session scan A ceb313fb6168

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository dvasyliev/ai-dev-tools-getting-started (21 stars, last pushed 4mo ago), with no licence file. It adds 60 tokens to every session and 920 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.

Related

Other skills, from other repositories

cc-commit-msg

结构化 git commit message 生成工作流,适用于显式 commit message、提交说明或 commit-msg 场景;不负责实际执行 git commit。.

doccker/cc-use-exp · 38 tokens

commit-summary

Generate Conventional Commit messages from staged or unstaged git changes, split unrelated changes into logical commits, detect breaking changes, and optionally create commits after approval. Use when writing commit messages, preparing commits, or committing local work.

shipshitdev/skills · 47 tokens

apm-issue-autopilot

Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…

microsoft/apm · 238 tokens

managing-git

Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.

CloudAI-X/claude-workflow-v2 · 46 tokens

git-master

MUST USE whenever a task needs a commit or git-history investigation. Covers atomic commits, staging, commit-message style, rebase, squash, fixup/autosquash, blame, bisect, reflog, git log -S/-G, and questions like who wrote this or when was this added. Do not use for ordinary code edits unless the user asks for git…

code-yeongyu/oh-my-openagent · 81 tokens

aidd-vcs:01:commit

Create an atomic git commit with conventional message format. Supports interactive mode (human-driven, may split commits, asks approval) and auto mode (agent-driven, no approval, single commit). Use when the user says "commit", "git commit", "create a commit", "commit my changes", "commit and push", or invokes…

ai-driven-dev/framework · 102 tokens