conventional-commit

A procedure for creating a commit from staged Git changes using a standard subject format such as feat(api): add endpoint. A commit is a saved group of changes in a Git repository.

In plain words
What is it for?
Use it when staged changes are ready to commit and need a typed, scoped subject under 72 characters.
Why use it?
It produces a clear, consistent commit message and checks what is actually staged before saving it.

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

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 484 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.00031 $0.00484
Opus 5 $0.00015 $0.00242
Sonnet 5 $0.00006 $0.00097
Haiku 4.5 $0.00003 $0.00048

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

Security

Grade A, and why

conventional-commit 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/conventional-commit/SKILL.md · 48 lines

What it actually says

Create Conventional Commit

Create a Conventional Commits message for the staged changes in this repository and commit them.

Workflow

  1. Inspect the staged state:
    • git diff --cached --name-only — staged files.
    • git diff --cached --stat — diff stat.
    • git diff --cached — full patch.
  2. If nothing is staged, say so and stop.
  3. Read the staged files or nearby context if the patch is ambiguous.
  4. Write one Conventional Commits subject:
    • Form: <type>(<scope>): <description> where <type> is feat, fix, chore, docs, refactor, test, perf, ci, build, style, or revert. <scope> is optional.
    • Imperative mood (add, not added).
    • Under 72 characters total.
    • Precise scope when it helps; omit if it adds no signal.
    • For a breaking change, append ! after the type/scope, e.g. feat(api)!: drop v1 endpoint.
  5. Run git commit -m "<subject>" with that exact subject, then read the short hash from the commit output (or git rev-parse --short HEAD).
  6. After success, print only these two lines:
Subject: <subject>
Commit: <hash>
  1. If the commit fails (pre-commit hook, no staged changes), show the failure briefly and stop. Do not amend.

Gotchas

  • Keep the final response plain text and compact.
  • Never run git push from this skill.

Documentation

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 · 48 lines · 31 tokens per session scan A e394646c86ae

Subscribe to this mod's changes

conventional-commit is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 484 once invoked, about $0.0002 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

dotfiles-bootstrap

Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.

sebastienrousseau/dotfiles · 88 tokens

vibe

Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…

sebastienrousseau/dotfiles · 137 tokens

aiq-research

Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.

laurigates/dotfiles · 25 tokens

obsidian-bases

Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.

laurigates/dotfiles · 49 tokens

telegram

Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…

laurigates/dotfiles · 117 tokens

chezmoi-expert

Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…

laurigates/dotfiles · 88 tokens