A workflow for creating short conventional commit messages, which follow a shared format such as a change type and brief subject. It can inspect changes, run available pre-commit checks, stage files, and create commits.

Use it when staging and committing work, writing a commit message, running pre-commit checks, or deciding whether a change should be split into atomic commits.

It gives commits a consistent format and catches available checks before saving changes. It can also flag when one diff contains separate concerns that should become separate commits.

commit — Skill for Claude Code by rikdc/ai-skills

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 rikdc/ai-skills --skill commit

Clone the repo

git clone --depth 1 https://github.com/rikdc/ai-skills

Made for: Claude Code.

Or install git-workflow, the plugin that ships this one along with the rest of its 3 skills.

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/rikdc/ai-skills/commit/github.svg)](https://agentmods.dev/skills/rikdc/ai-skills/commit)

Your own site

<a href="https://agentmods.dev/skills/rikdc/ai-skills/commit"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/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/rikdc/ai-skills/commit"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/commit.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 766 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.00055	$0.00766
Opus 5.5	$0.00022	$0.00306
Sonnet 5.5	$0.00011	$0.00153
Haiku 4.5	$0.00006	$0.00077

Measured 1mo ago against content hash 47e3b3239ab0, 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.

plugins/git-workflow/skills/commit/SKILL.md · 103 lines

How it starts

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

Commit - Conventional Commit Messages

Creates commits with short conventional commit messages. Runs pre-commit checks and suggests splitting when the staged changes cover more than one concern.

Usage

/git-workflow:commit [--no-verify] [--help]

Workflow

Pre-commit checks (unless --no-verify): run make checks if available.
Git analysis: inspect staged files and git diff to identify the change.
Commit: write the message, then commit.

If nothing is staged, stage all modified files. If the diff covers distinct concerns, propose atomic commits before committing.

Message Rules

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

[body — only when required]

No emoji. Not in the subject, not in the body.
Subject: imperative mood, lower case, no trailing period, under 60 characters.
scope is optional; include it only when it disambiguates.
Default to a subject line alone. Most commits need nothing more.
Add a body only for information the diff cannot show: why the change was made, a breaking change, or an issue reference. Cap it at two short sentences or three bullets.
Never restate the diff, list touched files, summarise your process, or add closing commentary.

Types

feat: new feature
fix: bug fix, security fix, warning fix
docs: documentation
style: formatting
refactor: restructuring without behaviour change
perf: performance
test: tests
chore: tooling, dependencies, configuration
ci: CI/CD

Splitting Criteria

Propose separate commits when the staged changes mix concerns, mix types (feature + fix + docs), or are large enough that one message cannot describe them accurately.

Examples

Good:

feat(auth): add session refresh endpoint
fix(render): release texture handles on unmount
docs: document the scanner exit codes
refactor: collapse duplicate error wrapping

With a body, where the reason is not visible in the diff:

fix(scanner): match patterns case-insensitively

Uppercase AWS keys were slipping through, reported in #212.

Read the full file on GitHub · 103 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 · 103 lines · 55 tokens per session scan A 47e3b3239ab0

Subscribe to this mod's changes

commit is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 2d ago), licensed MPL-2.0. It adds 55 tokens to every session and 766 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.

Claude Code Commits Git and workflow claude-code-plugin

branch-and-worktree-workflow

Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…

cbrock84/headcount · 70 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

next-step

Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.

sd0xdev/sd0x-harness · 63 tokens

precommit

Pre-commit checks — lint:fix -> build -> test.

sd0xdev/sd0x-harness · 15 tokens

precommit-fast

Quick pre-commit checks — lint:fix -> test.