What is gen-commit-msg?

A command that creates a Git commit message from the changes already staged for commit. It can follow the repository's recent commit style and use categories such as feature, fix, documentation, or test.

Reviewing staged files and content, choosing a change category, inferring a scope from file paths, creating a commit, or amending the previous commit.

It removes the need to write a consistent summary and category by hand after preparing changes.

gen-commit-msg — Command by magic3007

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/magic3007/dotfiles/gen-commit-msg

Clone the repo

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

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

When invoked 836 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.00022	$0.00836
Opus 5	$0.00011	$0.00418
Sonnet 5	$0.00004	$0.00167
Haiku 4.5	$0.00002	$0.00084

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

Security

Grade A, and why

gen-commit-msg 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.

claude/commands/gen-commit-msg.md · 167 lines

How it starts

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

Generate Commit Message

Generate a well-formatted commit message based on staged changes.

Usage

/gen-commit-msg [--amend] [--scope <scope>]

Arguments:

--amend: Amend the previous commit instead of creating new
--scope <scope>: Force a specific scope (e.g., workflow, engine)

Workflow

Step 1: Analyze Changes

# Check staged files
git diff --cached --name-only

# Check staged content
git diff --cached

# Check recent commit style
git log --oneline -5

Step 2: Categorize Changes

Type	When to Use
`feat`	New feature or capability
`fix`	Bug fix
`docs`	Documentation only
`refactor`	Code change without feature/fix
`test`	Adding or fixing tests
`chore`	Build, deps, config changes
`perf`	Performance improvement

Step 3: Determine Scope

Infer scope from changed files:

src/ or lib/ → infer from subdirectory (e.g., src/auth/ → auth)
app/ or client/ → app or client
server/ or api/ → api
test/ or tests/ → test
docs/ → docs
config/ or conf/ → config
scripts/ → scripts
Multiple areas → omit scope or use broader term

Step 4: Generate Message

Format:

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

<body>

[Optional sections:]
Key changes:
- change 1
- change 2

Refs: #123, #456

Rules:

Subject: imperative mood, ~50-72 chars, no period
Body: explain "why" not "what", wrap at 72 chars
Key changes: bullet list of main modifications (for complex commits)
Refs: reference issues/PRs if applicable

Step 5: Confirm and Commit

Show preview:

─────────────────────────────────────
feat(workflow): add vision support to ImageProcessing

Add ImageProcessingWorkflow for vision-language processing.
Supports image inputs alongside text prompts.
─────────────────────────────────────

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

yesterday First seen · 167 lines · 22 tokens per session scan A 5ff25a60c6a2

Subscribe to this mod's changes

gen-commit-msg is a command published in the GitHub repository magic3007/dotfiles (10 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 836 once invoked, about $0.0001 per session on Opus 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 Testing Writing and docs dotfiles git-config neovim ranger tmux zsh

gen-commit-msg

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Generate Commit Message

Usage

Workflow

Step 1: Analyze Changes

Step 2: Categorize Changes

Step 3: Determine Scope

Step 4: Generate Message

Step 5: Confirm and Commit

What this file has done since we first saw it

Other commands, from other repositories

spec

issue-implement

pr

push-commit

commit

pr-address-reviews