What is git-workflow?

A set of rules for writing Git commits and organizing changes. Git is a tool that records code history, and a commit is one saved set of changes.

Use it when naming commits, separating work into atomic changes, reviewing files before committing, and checking that tests pass after each change.

It keeps project history easier to understand, review, revert, and troubleshoot. The rules discourage mixing unrelated work or saving incomplete changes together.

git-workflow — Skill for Claude Code by aigentive/RalphX

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 aigentive/RalphX --skill git-workflow

Clone the repo

git clone --depth 1 https://github.com/aigentive/RalphX

Made for: Claude Code.

Or install ralphx, the plugin that ships this one along with the rest of its 15 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aigentive/ralphx/git-workflow/github.svg)](https://agentmods.dev/skills/aigentive/ralphx/git-workflow)

Your own site

<a href="https://agentmods.dev/skills/aigentive/ralphx/git-workflow"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aigentive/ralphx/git-workflow"><img src="https://agentmods.dev/badge/skills/aigentive/ralphx/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 551 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00551
Opus 5.5	$0.00004	$0.00220
Sonnet 5.5	$0.00002	$0.00110
Haiku 4.5	$0.00001	$0.00055

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

plugins/app/skills/git-workflow/SKILL.md · 107 lines

How it starts

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

Git Workflow

Commit Message Format

<type>: <description>

[optional body]

[optional footer]

Types

feat: New feature
fix: Bug fix
refactor: Code change that neither fixes a bug nor adds a feature
test: Adding or updating tests
docs: Documentation only changes
chore: Changes to build process or auxiliary tools
style: Formatting, missing semi-colons, etc.

Examples

feat: add user authentication
fix: resolve race condition in task loading
refactor: extract validation logic to separate module
test: add integration tests for API endpoints
docs: update README with setup instructions
chore: update dependencies

Atomic Commits

Principles

One logical change per commit
Tests should pass after each commit
Can be reverted independently
Easy to understand in isolation

Signs of Good Atomicity

Commit message fits in one line
All files relate to the same change
No "and" needed to describe the change
Tests still pass if commit is reverted

What to Avoid

"Fix several bugs"
Mixing refactoring with features
Incomplete changes
Unrelated file changes

Workflow

Before Committing

Review changes: git diff
Follow the target project's local instructions and run only the focused validation required for the change
Run scoped linting when the target project requires it
Stage specific files: git add <files>

Commit Checklist

Changes are tested
Tests pass
Lint passes
Message follows convention
No sensitive data included

Commands

# View changes
git status
git diff
git diff --staged

# Stage changes
git add <file>           # Specific file
git add -p              # Interactive staging (avoid -A)

# Commit
git commit -m "type: description"

# View history
git log --oneline -10
git log --stat -3

Safety Rules

Never

Force push to main/master
Commit secrets or credentials
Commit without the target project's required focused validation
Use git add -A blindly

Read the full file on GitHub · 107 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.

1mo ago First seen · 107 lines · 9 tokens per session scan A 1e8de5b78dd2

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository aigentive/RalphX (5 stars, last pushed 24d ago), licensed Apache-2.0. It adds 9 tokens to every session and 551 once invoked, about $0.0000 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-31.

Git and workflow

git-workflow