agentmods.dev

write-intentional-commit-message

write-intentional-commit-message is a skill for Claude Code, Codex from andrewsrigom/agent-skills. It costs 55 tokens per session (808 once invoked), scanned A, original, MIT.

A guide for choosing clear Conventional Commit messages, a shared format such as `feat` or `fix` followed by a short description. It also covers whether related changes should be split or an existing commit amended.

In plain words
What is it for?
Use it when writing, renaming, reviewing, splitting, or amending commits. It helps select the type, optional scope, and concise summary based on what changed.
Why use it?
It prevents commit titles from hiding the purpose of a change or using the wrong category. Clear messages make project history easier to understand and review.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 2repo 7mo ago A scan 55 tokens original MIT

Good fit Use it when writing, renaming, reviewing, splitting, or amending commits. It helps select the type, optional scope, and concise summary based on what changed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andrewsrigom/agent-skills/write-intentional-commit-message
View source ↗ andrewsrigom/agent-skills andrewsrigom.github.io
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.

Any agent
npx skills add andrewsrigom/agent-skills --skill write-intentional-commit-message
Clone the repo
git clone --depth 1 https://github.com/andrewsrigom/agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-intentional-commit-message

README.md
[![agentmods](https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/write-intentional-commit-message/github.svg)](https://agentmods.dev/skills/andrewsrigom/agent-skills/write-intentional-commit-message)
Your own site
<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/write-intentional-commit-message"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/write-intentional-commit-message/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-intentional-commit-message

Your own site · 80×15
<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/write-intentional-commit-message"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/write-intentional-commit-message.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 808 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00055 $0.00808
Opus 5.5 $0.00022 $0.00323
Sonnet 5.5 $0.00011 $0.00162
Haiku 4.5 $0.00006 $0.00081

Measured 2mo ago against content hash 76c990d437aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-intentional-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 2mo 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.

engineering/write-intentional-commit-message/SKILL.md · 94 lines

How it starts

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

Write Intentional Commit Message

Use this skill when the task is to name a commit well, not merely make it parse.

Scope

  • choosing the right Conventional Commit type
  • deciding whether the work should be one commit or several
  • writing concise summaries with real intent
  • deciding when to amend instead of adding another commit
  • avoiding vague commit titles that hide the actual change

Routing cues

  • write this commit message, pick the right conventional commit type, rename this commit, split this work into commits, amend or new commit, or review whether a commit title is misleading -> use this skill
  • if the task is about installing commit hooks or enforcing commit syntax in a repo -> use setup-conventional-commits

Default path

  1. Read the diff or change summary first.
  2. Describe the effect of the change in one sentence.
  3. Choose the type by the effect:
    • feat for a new user-facing or developer-facing capability
    • fix for a bug fix
    • refactor for structural change without a net-new capability
    • docs for documentation-only change
    • chore for tooling, CI, or maintenance work
  4. Add a scope only if it makes the message clearer.
  5. Keep the summary short, specific, and action-oriented.
  6. If the diff contains multiple unrelated effects, split the commit instead of forcing one misleading title.

When to deviate

  • Use a broader type only when the repo has an explicit convention that differs from the default mapping.
  • Skip scope if it adds noise or duplicates the summary.
  • Keep one larger commit only when the subchanges are tightly coupled and separating them would reduce clarity.
  • Amend instead of adding a follow-up commit when the new changes are still part of the same original intent.

Guardrails

  • choose the type by what changed in behavior or capability, not by which files were touched
  • the summary should name the real change, not the activity used to produce it
  • avoid one-word summaries like cleanup or updates
  • if the commit message feels generic, the commit is probably too broad or the summary is too weak

Read the full file on GitHub · 94 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 94 lines · 55 tokens per session scan A 76c990d437aa

Subscribe to this mod's changes

write-intentional-commit-message is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 808 once invoked, about $0.0002 per session on Opus 5.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.

CommitsGit and workflow
Related

write-intentional-commit-message compared with skills from other repositories

write-intentional-commit-message next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
write-intentional-commit-messageandrewsrigom/agent-skillsSkill27mo agoMITA55Claude Code, Codex
create-prprisma/ormSkill48kyesterdayApache-2.0A48Claude Code, Codex
git-commitThinkInAIXYZ/deepchatSkill6.4kyesterdayApache-2.0A15Claude Code, Codex
repo-syncdavidondrej/skillsSkill4.3kyesterdayMITA25Claude Code, Codex
engineer-bot-opsmakecindy/cindySkill9.4ktodayApache-2.0A57Claude Code, Codex
mcore-split-prNVIDIA/skillsSkill3.9kyesterdayApache-2.0A25Claude Code
git-commit-writermergisi/awesome-openclaw-agentsSkill4.1k3d agoMITA53Claude Code, Codex