git-workflow

git-workflow is a skill for Claude Code from fmflurry/settings-opencode. It costs 42 tokens per session (1,019 once invoked), scanned A, original, MIT.

A set of rules for handling Git work through a dedicated Git specialist.

In plain words
What is it for?
Naming branches, staging changes, writing conventional commit messages, committing, pushing, and preparing pull requests.
Why use it?
It provides a consistent process for branches, commits, pushes, and pull requests without mixing repository operations into other development work.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; mentions OpenCode.

Good fit Naming branches, staging changes, writing conventional commit messages, committing, pushing, and preparing pull requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fmflurry/settings-opencode/git-workflow
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 fmflurry/settings-opencode --skill git-workflow
Clone the repo
git clone --depth 1 https://github.com/fmflurry/settings-opencode

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.

agentmods badge for git-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/fmflurry/settings-opencode/git-workflow/github.svg)](https://agentmods.dev/skills/fmflurry/settings-opencode/git-workflow)
Your own site
<a href="https://agentmods.dev/skills/fmflurry/settings-opencode/git-workflow"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/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.

agentmods 80×15 button for git-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/fmflurry/settings-opencode/git-workflow"><img src="https://agentmods.dev/badge/skills/fmflurry/settings-opencode/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,019 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00042 $0.01019
Opus 5.5 $0.00017 $0.00408
Sonnet 5.5 $0.00008 $0.00204
Haiku 4.5 $0.00004 $0.00102

Measured 1mo ago against content hash 952a758fcb15, 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 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.

.claude/skills/git-workflow/SKILL.md · 132 lines

How it starts

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

Git Workflow Skill

Use this skill whenever the task involves git.

When to Activate

  • Creating or renaming branches
  • Staging changes
  • Writing commit messages
  • Creating commits
  • Pushing branches
  • Preparing pull requests
  • Reviewing branch names or commit message format

Required Delegation

When git work is needed, delegate to the dedicated git-specialist subagent via the /git command.

  • Do not handle substantive git workflow directly in the main agent when /git can handle it.
  • Use the git-specialist agent for branch naming, commit message drafting, staging, commits, and pushes.
  • Keep non-git implementation work in the main agent, then switch to /git for repository operations.
  • If you are already the git-specialist agent, execute the git task directly and do not re-delegate it.

Commit Convention

Every commit message must follow this format:

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

[optional body]

[optional footer(s)]

When scope is not useful or not clear, this no-scope form is also valid:

<type>: <short summary>

Allowed Types

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect behavior, such as formatting
  • refactor: Code changes that neither fix a bug nor add a feature
  • test: Adding or correcting tests
  • chore: Maintenance tasks such as tooling or build updates

Commit Rules

  • English only: subject and body MUST be English, even when the diff or conversation is French.
  • Prefer including a meaningful scope when the affected area is clear
  • Omit scope instead of inventing one when it is not clear
  • Use a concise present-tense summary
  • Keep the summary focused on intent, not a file-by-file changelog
  • Match the type to the actual purpose of the change

Examples

  • feat(api): add user authentication endpoint
  • fix(auth): prevent empty login submission
  • chore(settings): sync opencode configuration

Branch Convention

Read the full file on GitHub · 132 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. 1mo ago Changed · +1 lines 952a758fcb15
  2. 1mo ago First seen · 131 lines · 42 tokens per session scan A 2319ffe84791

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,019 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories