commit-message

A guide for writing Git commit messages, based on the changes already staged for commit.

In plain words
What is it for?
It is used whenever changes are being committed, including staging and committing or pushing finalized code.
Why use it?
It ensures commit messages are short, specific, and consistently formatted, while allowing a project hook to approve the commit.

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

Made for: Claude Code, Codex.

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 279 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.00078 $0.00279
Opus 5 $0.00039 $0.00139
Sonnet 5 $0.00016 $0.00056
Haiku 4.5 $0.00008 $0.00028

Measured 2d ago against content hash 0fdc77303b32, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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/skills/commit-message/SKILL.md · 30 lines

What it actually says

Generating Commit Messages

Process

  1. Run git diff --staged to see all staged changes
  2. Analyze what changed and why
  3. Generate a commit message following the format below
  4. Only then run git commit, always appending # via-skill to the command so the project's PreToolUse hook allows it through. Example: git commit -m "Add JWT auth middleware" #via-skill

Format

Summary line (under 50 characters)

  • Present tense imperative mood: "Add", "Fix", "Update", "Remove"
  • Specific and descriptive — no generic messages

Example

Add JWT authentication middleware

Forbidden

  • No "Generated with Claude Code"
  • No "Co-Authored-By: Claude [email protected]"
  • No vague messages like "Update files" or "Fix issues"
  • No Body in commit messages
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 · 30 lines · 78 tokens per session scan A 0fdc77303b32

Subscribe to this mod's changes

commit-message is a skill published in the GitHub repository Haris0059/ibu-mcp (2 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 279 once invoked, about $0.0004 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

prs

Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.

google-gemini/gemini-cli · 27 tokens

ocx

Drive a running opencodex (ocx) proxy from the CLI — account pools, provider routing, model catalog, usage and cost attribution, request logs, access keys, storage cleanup, and the management API. Use when a task involves controlling or inspecting an opencodex proxy rather than editing the opencodex codebase.…

lidge-jun/opencodex · 0 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/obsidian-mcp-server · 82 tokens

close-task-commit-push-pr

Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.

devoxx/DevoxxGenieIDEAPlugin · 64 tokens

git-commit-push-pr

Commit all changes, push to remote, and open a pull request in one go. Use when the user says "commit push pr", "ship it", "open a pr", or invokes /git-commit-push-pr.

devoxx/DevoxxGenieIDEAPlugin · 53 tokens

micro-commit

Enforces strict, atomic commit hygiene. Splits large diffs into logical, revertible units.

winstonkoh87/Athena-Public · 24 tokens