gen-commit-msg

A commit-message generator that reads staged Git changes and writes a message using Conventional Commits, a common format for describing software changes consistently.

In plain words
What is it for?
Preparing commit messages from staged files, choosing an appropriate change type and scope, and amending the previous commit when requested.
Why use it?
It avoids guessing whether a change is a feature, fix, documentation update, test, or other category. It also helps keep commit history clear and consistent with the repository's existing style.

Skill for Claude CodeCodex

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 skills/magic3007/dotfiles/gen-commit-msg
Any agent
npx skills add magic3007/dotfiles --skill gen-commit-msg
Clone the repo
git clone --depth 1 https://github.com/magic3007/dotfiles

Made for: Claude Code, Codex.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 677 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.00019 $0.00677
Opus 5 $0.00010 $0.00338
Sonnet 5 $0.00004 $0.00135
Haiku 4.5 $0.00002 $0.00068

Measured yesterday against content hash 07eebe847901, 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/skills/gen-commit-msg/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 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

Invoke with /gen-commit-msg or when the task matches.

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, ask user to confirm, then execute:

git commit -m "$(cat <<'EOF'
<message>
EOF
)"

Examples

Single file fix:

fix(auth): handle null user in login validation

Return proper error instead of raising exception when
user object is null during authentication.

Read the full file on GitHub · 126 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. yesterday First seen · 126 lines · 19 tokens per session scan A 07eebe847901

Subscribe to this mod's changes

gen-commit-msg is a skill published in the GitHub repository magic3007/dotfiles (10 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 677 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.

Related

Other skills, from other repositories

assess-quality

Foundational quality framework: the five questions (readable, easy to start, expands without bloat, consistent, intentional) every other dev skill is judged against, plus the dual-audience and workshop principles. Use when onboarding to a project, defining a quality bar, setting an assessment checklist, or arbitrating…

urmzd/dotfiles · 120 tokens

create-oss-skill

Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.

urmzd/dotfiles · 63 tokens

orchestrate-agents

Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel…

urmzd/dotfiles · 83 tokens

extend-oss-skills-to-claude

Extend standard agentskills.io skills with Claude Code-specific features. Invocation control, subagent execution, dynamic context injection, string substitutions, model/effort overrides, and deployment scoping. Use when adapting a portable skill for Claude Code, adding Claude-specific frontmatter, setting up subagent…

urmzd/dotfiles · 74 tokens

merge-ready

Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness…

urmzd/dotfiles · 208 tokens

scaffold-project

Generates cross-language standard files (README, AGENTS.md, LICENSE, CONTRIBUTING.md, SECURITY.md, sr.yaml, .envrc, llms.txt), documentation conventions, and project structure, then dispatches to language-specific scaffolds. Use first for cross-language standard files and structure, THEN load the matching scaffold…

urmzd/dotfiles · 137 tokens