A command that helps create a Git commit, which is a saved checkpoint of changes in a Git repository. It follows the Conventional Commits style, a shared format for writing commit messages.

Use it to inspect changes, suggest commit messages, stage files after approval, and create the commit.

It helps turn a set of code changes into a clear, reviewable commit while checking for sensitive files and information first.

gitcommit — Command for Claude Code by koolamusic/claudefiles

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.

Clone the repo

git clone --depth 1 https://github.com/koolamusic/claudefiles

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/koolamusic/claudefiles/gitcommit/github.svg)](https://agentmods.dev/commands/koolamusic/claudefiles/gitcommit)

Your own site

<a href="https://agentmods.dev/commands/koolamusic/claudefiles/gitcommit"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/gitcommit/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/commands/koolamusic/claudefiles/gitcommit"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/gitcommit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 831 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.00011	$0.00831
Opus 5.5	$0.00004	$0.00332
Sonnet 5.5	$0.00002	$0.00166
Haiku 4.5	$0.00001	$0.00083

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

Security

Grade A, and why

gitcommit 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.

commands/gitcommit.md · 100 lines

How it starts

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

Context

Current branch: !git branch --show-current
Git status: !git status --short
Staged changes: !git diff --cached --stat
Unstaged changes: !git diff --stat
Full diff: !git diff HEAD
Recent commits: !git log --oneline -5

Your task

Check if there are changes to commit; if none, inform the user and stop
Review the diff for sensitive data (API keys, passwords, .env files) — warn if found
Analyze changes to understand the nature and purpose
Generate 3 commit message candidates per the Message format section below
Present candidates to the user and ask which to use (or suggest edits)
Stage unstaged changes if user confirms
Execute git commit with the selected message
If pre-commit hooks fail, report the error and offer to fix

Message format

Conventional Commits. Why over what — the diff already shows what changed. Match project convention (use the recent-commits context above to detect capitalization, scope style, and trailer usage).

Subject line

Format: <type>(<scope>): <imperative summary> — scope optional
Append ! after type/scope to mark a breaking change: feat(api)!: or feat!:
Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"
≤50 chars when possible, hard cap 72
No trailing period

Types

feat — new feature
fix — bug fix
refactor — code restructuring without behavior change
perf — performance improvement
docs — documentation
test — tests
chore — maintenance, tooling, deps
build — build system, packaging
ci — CI configuration
style — formatting, whitespace
revert — reverts a prior commit

Body

Skip when the subject is self-explanatory
Add when the why isn't obvious from the diff
Wrap at 72 chars; bullets - not *
Reference issues/PRs at end as trailers: Closes #42, Refs #17

Mandatory body (regardless of how obvious it seems): breaking changes, security fixes, data migrations, reverts.

Read the full file on GitHub · 100 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 · 100 lines · 11 tokens per session scan A b4e7ac2fc5ed

Subscribe to this mod's changes

gitcommit is a command published in the GitHub repository koolamusic/claudefiles (130 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 831 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-30.

Commits Git and workflow

gitcommit