write-commit-message

A guide for writing Git commit messages in Conventional Commits format, a shared style such as `fix(scope): describe change`. It defines message types, length, wording, and optional details.

In plain words
What is it for?
Use it when creating commits so messages clearly state the kind of change and its purpose.
Why use it?
It makes the project history easier to scan, search, and use with tools that infer release changes from commit messages.

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/eveld/claude/write-commit-message
Any agent
npx skills add eveld/claude --skill write-commit-message
Clone the repo
git clone --depth 1 https://github.com/eveld/claude

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 285 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.00285
Opus 5 $0.00011 $0.00143
Sonnet 5 $0.00004 $0.00057
Haiku 4.5 $0.00002 $0.00028

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

Security

Grade A, and why

write-commit-message 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.

skills/write-commit-message/SKILL.md · 57 lines

What it actually says

Write Commit Message

Create git commit messages following the Conventional Commits format.

Template

See templates/commit-message.md for the full template structure, format rules, and examples.

Quick Reference

Format:

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

[optional body]

[optional footer]

Common Types: feat, fix, docs, refactor, test, chore

Key Rules:

  • Subject < 72 characters
  • Use imperative mood ("add" not "added")
  • No period at end of subject
  • Body explains what and why, not how

Integration with Git Workflow

When user asks to commit or you're following git workflow:

  1. Run git status and git diff to see changes
  2. Analyze the nature of changes
  3. Draft commit message following format
  4. Use heredoc for proper formatting:
git commit -m "$(cat <<'EOF'
feat(auth): add JWT token refresh

Implements automatic token refresh mechanism.
EOF
)"

Benefits

  • Clear, scannable git history
  • Semantic versioning compatibility
  • Automatic changelog generation
  • Easy to search and filter commits
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 · 57 lines · 22 tokens per session scan A ce26b45765cc

Subscribe to this mod's changes

write-commit-message is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 285 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

code-indexing-pipeline

How Infigraph turns source into a graph — adding a language (tree-sitter vs ANTLR grammar-plugin), cross-file call resolution, SCIP compiler-grade enrichment, and file-watch/reindex triage. Use when adding language support, debugging unresolved calls or SCIP import, or triaging stale index/watcher issues.

intuit/infigraph · 70 tokens

review-pr-against-issue

Review one or more PRs against the GitHub issue(s) they claim to fix, including fetching PR branches directly when gh can't reach github.com (e.g. gh is authenticated to an enterprise host instead). Use whenever asked "does this PR fix issue.

intuit/infigraph · 61 tokens

analysis-subsystems

How Infigraph's multi-repo/group mode and taint analysis work internally — HTTP contract extraction heuristics, cross-service edge linking, combined-graph merge, remote mode, plus taint's line-based tracking and sanitizer heuristic. Use when working on crates/infigraph-core/src/multi/ or src/taint/, or investigating…

intuit/infigraph · 80 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

golden-rss

Use when testing the rss golden build.

yusufkaraaslan/Skill_Seekers · 12 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens