git-workflow

git-workflow is a skill for Claude Code from hiromaily/go-crypto-wallet. It costs 31 tokens per session (2,764 once invoked), scanned A, original, MIT.

A Git workflow covering branches, commit conventions, and pull requests. Git is a tool for tracking code changes and collaborating on them.

In plain words
What is it for?
Use it when making code changes, creating task branches, preparing commits, or opening pull requests.
Why use it?
It reduces mistakes such as working on the wrong branch or using inconsistent project workflows.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it when making code changes, creating task branches, preparing commits, or opening pull requests.

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

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/hiromaily/go-crypto-wallet/git-workflow/github.svg)](https://agentmods.dev/skills/hiromaily/go-crypto-wallet/git-workflow)
Your own site
<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/git-workflow"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/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/hiromaily/go-crypto-wallet/git-workflow"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,764 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.02764
Opus 5 $0.00015 $0.01382
Sonnet 5 $0.00006 $0.00553
Haiku 4.5 $0.00003 $0.00276

Measured 7d ago against content hash a1cae305440f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 7d 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 · 435 lines

How it starts

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

Git Workflow

Standard Git workflow for all tasks in this repository.

⚠️ MANDATORY: Check Branch Before Starting ANY Task

This is the FIRST step for ANY task that involves code changes.

Before writing any code or making any changes, you MUST check the current branch:

git branch --show-current

Decision Flow

Current Branch?
    │
    ├─ main → ❌ DO NOT work here
    │         → Create a new branch first (see "Creating a New Branch")
    │
    ├─ Feature branch for this task → ✅ Continue working
    │
    └─ Different feature branch → ⚠️ Ask user which branch to use

If on main Branch

NEVER make changes directly on main. Always create a new branch first:

# 1. Ensure main is up to date
git fetch origin
git reset --hard origin/main

# 2. Create new branch
git checkout -b {type}/{brief-description}-{issue-number}

If on Wrong Feature Branch

Ask the user:

"You are currently on branch {current-branch}. Should I:

  1. Continue working on this branch?
  2. Switch to main and create a new branch for this task?"

Example Check Output

$ git branch --show-current
main
# → Must create new branch before any work!

$ git branch --show-current
feature/add-taproot-support-123
# → OK to continue if this is the correct branch for the task

Branch Management

Creating a New Branch

Always create from latest main:

git fetch origin
git checkout main
git reset --hard origin/main
git checkout -b {type}/{brief-description}-{issue-number}

Branch Naming Convention

Format: {type}/{brief-description}-{issue-number}

  • Description should be short and meaningful (use kebab-case)
  • Issue number at the end (just the number, no "issue-" prefix)
Type Prefix Example
Feature feature/ feature/add-taproot-support-123
Bug fix fix/ fix/db-connection-error-456
Refactoring refactor/ refactor/clean-arch-layer-789
Documentation docs/ docs/update-readme-311
DevOps/CI ci/ ci/add-lint-workflow-100
Chore chore/ chore/update-deps-200

Read the full file on GitHub · 435 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. 7d ago First seen · 435 lines · 31 tokens per session scan A a1cae305440f

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 2,764 once invoked, about $0.0002 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-09-01.

Related

Other skills, from other repositories

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/coingecko-mcp-server · 82 tokens

agent-wallet

Operate a non-custodial blockchain wallet on-chain (EVM and Bitcoin), no exchange or MetaMask. Create or import a wallet, balances, send native/ERC-20/BTC, swap tokens, compile/deploy/call Solidity. Trigger on wallet, crypto, ETH, BTC, ERC-20, token, send, transfer, swap, trade, Solidity, contract, on-chain, testnet…

hec-ovi/blockchain-skill · 93 tokens

agent-solidity

Write, audit and deploy Solidity smart contracts through a gated multi-step workflow (spec, threat model, design, implementation, in-process EVM proof, security audit, deployment), with a local EVM sandbox that needs no Foundry, Hardhat, anvil, node or funds. Trigger on Solidity, smart contract, .sol, ERC-20, ERC-721…

hec-ovi/blockchain-skill · 122 tokens

pqc-scan

Inventory the cryptography in a codebase that a quantum computer would break, and report what the scan could not read. Use when asked about post-quantum readiness, cryptographic inventory, a CBOM, or which algorithms a project signs with.

StanimirTenev/qrp-mcp · 50 tokens

git-workflow-management

Git workflow automation skill for commit message generation, branch management, pre-commit checks, and change history analysis.

XSpoonAi/spoon-awesome-skill · 26 tokens

git-commit-semantic

A skill for writing semantic git commit messages based on Conventional Commits. Use when creating commit messages to ensure clarity and consistency.

XSpoonAi/spoon-awesome-skill · 31 tokens