A set of instructions for creating Git commit messages, the short records that describe code changes, according to repository rules or the Conventional Commits format.

Use it to review pending changes, stage only files for the current task, draft a commit message, and wait for approval before committing.

It helps prevent unrelated files, security concerns, or temporary changes from being included accidentally and keeps commit messages consistent.

commit — Command by shunk031

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.

agentmods

npx agentmods add commands/shunk031/dotfiles/commit

Clone the repo

git clone --depth 1 https://github.com/shunk031/dotfiles

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

When invoked 501 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00000	$0.00501
Opus 5	$0.00000	$0.00251
Sonnet 5	$0.00000	$0.00100
Haiku 4.5	$0.00000	$0.00050

Measured yesterday against content hash e3a03552577d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

home/dot_config/claude/commands/commit.md · 36 lines

What it actually says

Commit changes to Git

Step 1: Review all the uncommited changes in the current session.
Step 2: Notify the user if there are:
- Files with security concerns
- Files with temporary changes
Step 3: If there are files detected in Step 2, stop and let the user decise what to do next. Else, process to step 4.
Step 4: Add only the files relevant to the current task to staging. Never stage unrelated staged, unstaged, or untracked changes; if unrelated changes exist, list the files you are leaving out. Respect .gitignore and similar files.
Step 5: Write a commit message following Conventional Commits guideline below
Step 6: Ask if user approves the message. Give 3 options:
- Approve
- Regenerate
- I will write the commit message myself
Step 7:
- If user chose Approve on step 6, commit the changes with the generated message.
- If user chose Regenerate, re-run from step 5.
- If user chose to write commit message themselves, run git commit. It should open a text editor so that the user can write their commit message.

Conventional Commits guideline

Follow the Commit messages rule in the repository AGENTS.md when present; otherwise use the Conventional Commits 1.0.0 summary below.

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types: feat (new feature, SemVer MINOR), fix (bug fix, SemVer PATCH), plus build, chore, ci, docs, style, refactor, perf, test, and others.
Description: lowercase, imperative, and immediately after the <type>(<scope>): prefix, e.g. fix(parser): handle multiple spaces in string.
Body: optional free-form paragraphs, starting one blank line after the description.
Footers: optional git-trailer style lines, e.g. Refs: #123.
Breaking changes: mark with ! after the type/scope (feat(api)!: ...) or an uppercase BREAKING CHANGE: footer (SemVer MAJOR).

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.

yesterday First seen · 36 lines · 0 tokens per session scan A e3a03552577d

Subscribe to this mod's changes

commit is a command published in the GitHub repository shunk031/dotfiles (148 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 501 tokens. 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.

Code review Git and workflow Planning chezmoi dotfiles powerlevel10k tmux-conf zsh zshrc

commit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Commit changes to Git

Conventional Commits guideline

What this file has done since we first saw it

Other commands, from other repositories

test-coverage

commit

create-pr

clipboard

ssh-find

ssh-keys