New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git Workflow

by hiromaily in hiromaily/go-crypto-wallet

Git branch management, commit conventions, and PR creation workflow.

MITAuto-check passedDevelopment

Install Git Workflow

skills CLI
$ npx skills add hiromaily/go-crypto-wallet --skill git-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hiromaily/go-crypto-wallet git-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/git-workflow .claude/skills/git-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-workflow
GitHub stars
128
Token cost
~2.9k tokens
SKILL.md length
648 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Git branch management, commit conventions, and PR creation workflow.

  • Works in 3 steps: Run Verification Commands → Complete Self-Review Checklist → Confirm Before Commit
  • All tasks that require code changes
  • SKILL.md covers ⚠️ MANDATORY: Check Branch…, Branch Management, Commit Conventions and Pull Request Creation, plus 2 more sections
  • Calls git, make and gh

What it does

Git Workflow is an agent skill from hiromaily/go-crypto-wallet. Git branch management, commit conventions, and PR creation workflow. Use for all tasks that require code changes, regardless of language or scope.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow, Commit messages and Pull requests. The repository describes itself as: Cryptocurrency wallet for trading for Bitcoin, Bitcoin cash, Ethereum, ERC20, XRP Leger (Ripple). The licence is MIT.

When your agent uses it

  • All tasks that require code changes
  • Regardless of language

Example prompts

  • “/git-workflow”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Run Verification Commands
  2. Complete Self-Review Checklist
  3. Confirm Before Commit

What it can do on your machine

Read from SKILL.md and the folder at commit 798ab10. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • make
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • conventionalcommits.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Workflow loads about 2.9k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 648 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hiromaily/go-crypto-wallet at commit 798ab10, republished under its MIT licence (© hiromaily). 648 words, ~2,893 tokens.

Download SKILL.mdSave it as .claude/skills/git-workflow/SKILL.md (or your agent's skills folder).
name
git-workflow
description
Git branch management, commit conventions, and PR creation workflow. Use for all tasks that require code changes, regardless of language or scope.

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:

bash
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:

bash
# 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
bash
$ 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:

bash
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)
TypePrefixExample
Featurefeature/feature/add-taproot-support-123
Bug fixfix/fix/db-connection-error-456
Refactoringrefactor/refactor/clean-arch-layer-789
Documentationdocs/docs/update-readme-311
DevOps/CIci/ci/add-lint-workflow-100
Chorechore/chore/update-deps-200
Branch Rules
  • Always from main: Never branch from feature branches
  • One issue = One branch: Create only one branch per issue
  • Short-lived: Merge within days, not weeks
  • Delete after merge: Keep repository clean
⚠️ Important: No Multiple Branches Per Issue

Do NOT create multiple branches for the same issue.

❌ Prohibited Pattern:
  issue-123 → fix/first-attempt-123
            → fix/second-attempt-123  ← Do NOT create this
            → fix/another-fix-123     ← Do NOT create this either

✅ Correct Pattern:
  issue-123 → fix/description-123
            → Create PR → Review → Merge
            → (If needed) Create new issue with new branch
Pre-Work Verification

Before creating a new branch, always check the following:

bash
# 1. Check for existing branches
git branch -a | grep "{issue-number}"

# 2. Check for existing PRs
gh pr list --search "{issue-number}"
  • If existing branch exists: Continue working on that branch
  • If existing PR exists: Merge the PR before starting new work
  • If nothing exists: OK to create a new branch

Commit Conventions

This project uses Conventional Commits format. Commit messages are validated by lefthook commit-msg hook.

Format
{type}({scope}): {brief description}

- {detail 1}
- {detail 2}

Closes #{issue_number}
Types (Required)
TypeDescriptionRelease Impact
featNew featureMINOR
fixBug fixPATCH
docsDocumentation only-
refactorCode refactoring (no feature/fix)-
testAdding or updating tests-
ciCI/CD changes-
choreMaintenance tasks-
buildBuild system changes-
perfPerformance improvementsPATCH
styleCode style (formatting, etc.)-
revertRevert a previous commit-
Breaking Changes

Add ! after type/scope to indicate breaking changes:

bash
feat(btc)!: change address format to bech32m only
fix!: remove deprecated API endpoint
Scope (Optional)

The following are suggested scopes, but other alphanumeric scopes are also permitted.

ScopeDescription
btcBitcoin-related
bchBitcoin Cash-related
ethEthereum-related
xrpXRP-related
dbDatabase
apiAPI changes
cliCLI changes
prPR review fixes
Examples
bash
# Feature with scope
git commit -m "feat(btc): add taproot address support

- Add bech32m encoding
- Update address validation

Closes #123"

# Bug fix without scope
git commit -m "fix: resolve database connection timeout

- Increase pool timeout
- Add retry logic

Closes #456"

# Documentation
git commit -m "docs: update architecture guide

- Add layer diagram
- Clarify dependency rules

Closes #789"

# Breaking change
git commit -m "feat(btc)!: require bech32m for all taproot addresses

BREAKING CHANGE: Legacy address format no longer supported

Closes #999"
Validation Error

If commit message validation fails:

ERROR: Commit message does not follow Conventional Commits format.

Expected format: <type>(<scope>): <description>

Types: feat, fix, docs, refactor, test, ci, chore, build, perf, style, revert

Examples:
  feat(btc): add taproot address support
  fix: resolve database connection timeout
  docs: update architecture guide
  refactor(api): reorganize endpoint handlers

Your commit message: <your-invalid-commit-message>

Pull Request Creation

⚠️ MANDATORY: Ask Before Creating PR

Always ask the user before creating a PR.

Multi-phase tasks create multiple commits on a single branch. Do not create a PR until all commits are complete.

After commits are pushed, ALWAYS ask:
> "Would you like me to create a PR? Or is there additional work to do?"
Show full SKILL.md (248 more words)Show less
When to Ask
SituationAction
Single commit taskAsk before creating PR
Multi-phase taskAsk after ALL phases are complete
User explicitly requests PRCreate PR without asking
Create PR
bash
git push -u origin {branch-name}

# Ask user: "Would you like me to create a PR?"
# Only proceed if user confirms

gh pr create --title "{type}: {description}" --body "$(cat <<'EOF'
## Summary
- {change 1}
- {change 2}

## Test plan
- [ ] Verification commands pass
- [ ] Manual testing completed

Closes #{issue_number}
EOF
)"
PR Title Format
{type}: {description} (Closes #{issue_number})

Examples:

  • feat: add taproot address support (Closes #123)
  • fix: resolve database connection timeout (Closes #456)
  • docs: update architecture guide (Closes #789)
PR Description Template
markdown
## Summary

- Brief description of changes

## Changes

- Change 1
- Change 2

## Test plan

- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)
- [ ] Manual testing completed

## Related

- Closes #{issue_number}
- Related to #{other_issue}

Pre-Commit Self-Review (Required)

Before EVERY commit, you MUST complete self-review:

Step 1: Run Verification Commands

Execute verification commands for the modified file types:

File TypeRequired Commands
Go (*.go)make go-lint && make tidy && make check-build && make go-test
TypeScript (*.ts)See typescript-development skill (Bun for xrpl-grpc-server, npm for eth-contracts)
Shell (*.sh)make shfmt
Makefilemake mk-lint
SQL/HCLmake atlas-fmt && make atlas-lint
Step 2: Complete Self-Review Checklist

Read the applicable language skill and verify ALL checklist items:

File TypeSkillSection to Check
Go (*.go)go-developmentSelf-Review Checklist
TypeScript/JStypescript-developmentSelf-Review Checklist
Shell (*.sh)shell-scriptsVerification Checklist
Makefilemakefile-updateVerification Checklist
SQL/HCLdb-migrationVerification Checklist
Step 3: Confirm Before Commit

Only proceed to commit after:

  • All verification commands pass
  • Self-review checklist is complete
  • No unresolved linter errors

⚠️ DO NOT commit until all steps are verified.

Safety Rules

Allowed Operations
  • git add - Stage changes
  • git commit - Create commits
  • git push - Push to remote
  • git checkout -b - Create branches
NOT Allowed Operations
  • git push --force - Never force push
  • git merge - Don't merge locally
  • git rebase on shared branches - Avoid rebasing
  • Direct commits to main - Always use PRs

Quick Reference

New Issue Workflow
bash
# 0. Check for existing branches/PRs (Required)
git branch -a | grep "{issue-number}"
gh pr list --search "{issue-number}"
# → If exists, continue working on that branch

# 1. Update main
git fetch origin && git checkout main && git reset --hard origin/main

# 2. Create branch (only if none exists)
git checkout -b {type}/{brief-description}-{issue-number}

# 3. Make changes...

# 4. Self-Review (REQUIRED - see "Pre-Commit Self-Review" section)
#    - Run verification commands for modified file types
#    - Complete self-review checklist from language skill
#    - Confirm no linter errors

# 5. Commit (only after self-review is complete)
git add <files>
git commit -m "{type}: {description}

Closes #{number}"

# 6. Push
git push -u origin {branch-name}

# 7. Ask user before creating PR (REQUIRED)
#    "Would you like me to create a PR? Or is there additional work?"
#    Only create PR if user confirms
gh pr create --title "{type}: {description}"
PR Review Fixes
bash
# Already on PR branch

# 1. Make fixes...

# 2. Self-Review (REQUIRED)
#    Run verification commands & complete checklist

# 3. Commit and push
git add <files>
git commit -m "fix(pr): address review comments"
git push

© hiromaily, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/git-workflow of hiromaily/go-crypto-wallet.

Open the folder on GitHubat commit 798ab10

Compare with similar skills

Git Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Workflow this skillhiromaily/go-crypto-wallet128—~2.9kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence
Commit And PR Messagessuperplanehq/superplane7.7k—~1.6kAutomated safety check: PassCustom licence
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0

Similar skills

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Commit And PR Messages

    superplanehq/superplane

    Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…

    7.7k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes

  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from hiromaily/go-crypto-wallet

All 17 skills in this repo

  • Bch Development

    hiromaily/go-crypto-wallet

    Bitcoin Cash (BCH) API implementation rules. An agent skill from hiromaily/go-crypto-wallet.

    128 GitHub stars~1.6k tokensUpdated 5 mo ago
    Auto-check passed

  • Btc Terminology

    hiromaily/go-crypto-wallet

    Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type).

    128 GitHub stars~1.3k tokensUpdated 5 mo ago
    Auto-check passed

  • DB Migration

    hiromaily/go-crypto-wallet

    Database schema and migration workflow. An agent skill from hiromaily/go-crypto-wallet.

    128 GitHub stars~652 tokensUpdated 5 mo ago
    Auto-check passed

  • Devops

    hiromaily/go-crypto-wallet

    CI/CD and DevOps workflow. An agent skill from hiromaily/go-crypto-wallet.

    128 GitHub stars~435 tokensUpdated 5 mo ago
    Auto-check passed

  • Docs Update

    hiromaily/go-crypto-wallet

    Documentation update workflow. An agent skill from hiromaily/go-crypto-wallet.

    128 GitHub stars~1.3k tokensUpdated 5 mo ago
    Auto-check passed

  • Fix PR Review

    hiromaily/go-crypto-wallet

    Address PR review comments by selecting appropriate skills based on modified files.

    128 GitHub stars~919 tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Git Workflow

What does Git Workflow do?

Git branch management, commit conventions, and PR creation workflow. Git Workflow is an agent skill from hiromaily/go-crypto-wallet. Git branch management, commit conventions, and PR creation workflow.

When should I use Git Workflow?

Git Workflow fits situations like: all tasks that require code changes; regardless of language.

How do I install Git Workflow in Claude Code?

Run `npx skills add hiromaily/go-crypto-wallet --skill git-workflow -a claude-code`. Or copy the skill folder (.claude/skills/git-workflow in hiromaily/go-crypto-wallet) into .claude/skills/git-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Git Workflow in Codex?

Run `npx skills add hiromaily/go-crypto-wallet --skill git-workflow -a codex`. Or copy the skill folder (.claude/skills/git-workflow in hiromaily/go-crypto-wallet) into .agents/skills/git-workflow in your project. Codex loads it when a task matches its description.

Can I use Git Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hiromaily/go-crypto-wallet --skill git-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-workflow, .gemini/skills/git-workflow, .github/skills/git-workflow and .opencode/skills/git-workflow in your project.

What does Git Workflow need to run?

Going by SKILL.md and its folder, Git Workflow needs the command-line tools its instructions call (git, make and gh).

Does Git Workflow access the network?

SKILL.md names 1 domain. As links in the text: conventionalcommits.org. This is read from the text; nothing was executed.

Is Git Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git Workflow use?

Git Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Workflow use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Workflow?

Skills that share tags, products or a category with Git Workflow: Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars) and Commit And PR Messages (superplanehq/superplane, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Workflow?

hiromaily (a GitHub user) maintains it in hiromaily/go-crypto-wallet, which has 128 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on April 22, 2026.

Source: hiromaily/go-crypto-wallet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.