gen-commit-msg

A command that creates a Git commit message from the changes staged for commit; Git is the version-control tool used to record code changes.

In plain words
What is it for?
Run /gen-commit-msg to create or amend a commit message, optionally setting a scope such as workflow or engine.
Why use it?
It removes the need to inspect staged files and decide on the commit wording and category by hand.

Command for Claude Code

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/areal-project/areal/gen-commit-msg
Clone the repo
git clone --depth 1 https://github.com/areal-project/AReaL

Made for: Claude Code.

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

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00877
Opus 5 $0.00011 $0.00439
Sonnet 5 $0.00004 $0.00175
Haiku 4.5 $0.00002 $0.00088

Measured 2d ago against content hash 9f2e91142141, 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 2d 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.

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

How it starts

The opening of the file, as written. The whole thing — 171 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
gov Governance or maintainer changes
style Formatting/style-only changes
refactor Code change without feature/fix
perf Performance improvement
test Adding or fixing tests
build Build system or dependencies
ci CI pipeline or workflow changes
chore Build, deps, config changes
revert Revert a previous commit

Step 3: Determine Scope

Infer scope from changed files:

  • areal/workflow/workflow
  • areal/engine/engine
  • areal/reward/reward
  • areal/dataset/dataset
  • areal/api/api
  • docs/docs
  • 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 RLVR

Add VisionRLVRWorkflow for vision-language RL training.
Supports image inputs alongside text prompts.
─────────────────────────────────────

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

  1. 2d ago First seen · 171 lines · 22 tokens per session scan A 9f2e91142141

Subscribe to this mod's changes

gen-commit-msg is a command published in the GitHub repository areal-project/AReaL (5,706 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 877 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-30.