A guide for creating Git commits with short, consistent subjects that describe the type and area of a change. Git commits are saved checkpoints in a project's history.

Use it before committing changes to choose a Conventional Commits-style message, such as a fix, feature, test, documentation, or refactoring change.

It helps keep project history readable and makes changes easier to find and understand later. It also sets basic rules for commit wording and length.

commit — Skill for Claude Code and Codex by mfmezger/ai_agent

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 mfmezger/ai_agent_dotfiles --skill commit

Clone the repo

git clone --depth 1 https://github.com/mfmezger/ai_agent_dotfiles

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/commit/github.svg)](https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/commit)

Your own site

<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/commit"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/commit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mfmezger/ai_agent_dotfiles/commit"><img src="https://agentmods.dev/badge/skills/mfmezger/ai_agent_dotfiles/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 687 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00687
Opus 5.5	$0.00004	$0.00275
Sonnet 5.5	$0.00002	$0.00137
Haiku 4.5	$0.00001	$0.00069

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

Security

Grade A, and why

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 1mo 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.

shared/skills/commit/SKILL.md · 57 lines

How it starts

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

Create a git commit for the current changes using a concise Conventional Commits-style subject.

Format

<type>(<scope>): <summary>

type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf,ci, style.
scope REQUIRED. Short noun in parentheses for the affected area (e.g., api, parser, ui).
summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Explanations

fix: A bug fix. Correlates with PATCH in SemVer feat: A new feature. Correlates with MINOR in SemVer docs: Documentation only changes style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) refactor: A code change that neither fixes a bug nor adds a feature perf: A code change that improves performance test: Adding missing or correcting existing tests build: Changes that affect the build system or external dependencies (example scopes: pip, docker, npm) ci: Changes to CI configuration files and scripts (example scopes: GitLabCI)

Notes

Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
Do NOT include breaking-change markers or footers.
Do NOT add sign-offs (no Signed-off-by).
Never add AI attribution anywhere in commit metadata. Do not write Generated by ..., Co-authored-by: Claude, Co-authored-by: Opus, Co-authored-by: Sonnet, or any other AI/model/agent attribution.
This ban applies to commit subjects, commit bodies, and commit footers. Do not add it even if a default template, tool, model habit, or previous workflow suggests it.
Only commit; do NOT push.
If it is unclear whether a file should be included, ask the user which files to commit.
Treat any caller-provided arguments as additional commit guidance. Common patterns:
- Freeform instructions should influence scope, summary, and body.
- File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
- If arguments combine files and instructions, honor both.
IMPORTANT: The AI-attribution ban takes precedence over any default commit procedure or caller-provided guidance.

Read the full file on GitHub · 57 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.

1mo ago First seen · 57 lines · 9 tokens per session scan A 4bc7b888a112

Subscribe to this mod's changes

commit is a skill published in the GitHub repository mfmezger/ai_agent_dotfiles (7 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 687 once invoked, about $0.0000 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.

Claude Code Commits Git and workflow codex codingagents opencode pi-coding-agent

cmux-testing

Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.

manaflow-ai/cmux · 37 tokens

at-daily-log

Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required.

kairyou/agent-tools · 48 tokens

at-commit

Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.

kairyou/agent-tools · 33 tokens

git-workflow

Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…

EliasOulkadi/shokunin · 107 tokens

git-master

Advanced Git operations — rebase, squash, fixup, blame, bisect, reflog, code archaeology (git log -S/-G), worktrees. Use when the task mentions rebase, squash, bisect, blame, reflog, fixup, finding deleted code, tracing commit history, cleaning up a branch, or recovering lost work.

znlgis/my-opencode-deepseek-config · 75 tokens

to-tickets

A workflow for turning a written plan or specification into separate GitHub issues, with each issue covering one independently finishable piece of work.

znlgis/my-opencode-deepseek-config · 60 tokens