A guide for writing Git commit messages, which record changes made to a code project. It uses a standard format with labels such as `feat` for new features and `fix` for bug fixes.

It helps write commit subjects, explanations, issue references, and notes about breaking changes when saving code changes.

It removes the guesswork from describing changes and keeps a project's history consistent and easier to search.

git-commit — Skill for Claude Code and Codex by DauQuangThanh

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 DauQuangThanh/hanoi-rainbow --skill git-commit

Clone the repo

git clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbow

Made for: Claude Code, Codex.

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/dauquangthanh/hanoi-rainbow/git-commit/github.svg)](https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/git-commit)

Your own site

<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/git-commit"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/git-commit/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/dauquangthanh/hanoi-rainbow/git-commit"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,044 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.00110	$0.01044
Opus 5.5	$0.00044	$0.00418
Sonnet 5.5	$0.00022	$0.00209
Haiku 4.5	$0.00011	$0.00104

Measured 1mo ago against content hash 740a60e2003a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-commit 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.

skills/git-commit/SKILL.md · 118 lines

How it starts

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

Git Commit

Generates well-structured git commit messages following conventional commit standards and best practices.

Key Principles

Be specific: Describe exactly what changed
Be consistent: Follow conventional commit format
Be atomic: One logical change per commit
Be clear: Write for others (including future you)
Be complete: Include why and context when needed
Be conventional: Follow standard format for automation

Standard Format

<type>(<scope>): <subject>

<body>

<footer>

Components:

type: Category of change (required) - feat, fix, docs, refactor, perf, test, build, ci, chore, style, revert
scope: Area affected (optional) - auth, api, ui, db, etc.
subject: Brief description (required, ≤50 chars)
body: Detailed explanation (optional, wrap at 72 chars)
footer: Breaking changes, issue refs (optional)

Basic Workflow

Choose the commit type:
- feat: New user-facing functionality
- fix: Bug fix for users
- docs: Documentation only
- refactor: Code restructuring without behavior change
- perf: Performance improvement
- test: Adding/updating tests
- build: Dependency/build system changes
- ci: CI/CD configuration changes
- chore: Maintenance tasks
- style: Code formatting
- revert: Reverting previous commit

Write subject line (imperative mood, ≤50 chars):

✅ feat(auth): add OAuth2 authentication
✅ fix(api): resolve race condition in user updates
❌ feat: added some stuff
❌ fix: bug fix

Add body if needed (explain why, not just what):
- Required for breaking changes
- Recommended for complex changes
- Wrap lines at 72 characters
Include footer:
- Breaking changes: BREAKING CHANGE: description
- Issue references: Closes #123, Fixes #456

Quick Examples

Simple feature:

feat(auth): add password reset endpoint

Bug fix with context:

Read the full file on GitHub · 118 lines

Files

What ships with it

13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 118 lines · 110 tokens per session scan A 740a60e2003a

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (17 stars, last pushed 9mo ago), licensed MIT. It adds 110 tokens to every session and 1,044 once invoked, about $0.0004 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.

Commits Git and workflow agentic-ai ai process software-development spec-driven spec-driven-development

speq-git-discipline

Read-only git guardrails. No history writes, verify changes before completing. Used by speq agents. Not for general git work.

marconae/speq-skill · 34 tokens

Phase 3 of the Tripod workflow, run repeatedly. Finds the first unchecked task in TASKS.md, implements it under the rules in CLAUDE.md, verifies its "Done when" condition, checks the box, and commits. Use when the user says "next task", "continue", "keep going", or invokes /tripod:next.

ayberkyasa/tripod · 74 tokens

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

paperclipai/paperclip · 39 tokens

agentic-jujutsu

Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.

ruvnet/ruflo · 26 tokens

github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

ruvnet/ruflo · 61 tokens

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens