A Git helper for saving staged code changes as a commit. Git commits are named snapshots of changes, and the guide uses standard labels such as feature, fix, or documentation.

Reviewing staged changes, writing a Conventional Commit message, committing them, and displaying the latest commit.

It turns the staged diff into a consistent commit message and checks the result after saving it.

commit — Skill for Claude Code by huzaifa525/claude-code-optimizer

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 huzaifa525/claude-code-optimizer --skill commit

Clone the repo

git clone --depth 1 https://github.com/huzaifa525/claude-code-optimizer

Made for: Claude Code.

Or install claude-code-optimizer, the plugin that ships this one along with the rest of its 25 skills, 4 hooks.

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/huzaifa525/claude-code-optimizer/commit/github.svg)](https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/commit)

Your own site

<a href="https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/commit"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/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/huzaifa525/claude-code-optimizer/commit"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 486 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.00021	$0.00486
Opus 5.5	$0.00008	$0.00194
Sonnet 5.5	$0.00004	$0.00097
Haiku 4.5	$0.00002	$0.00049

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

templates/.claude/skills/commit/SKILL.md · 72 lines

What it actually says

Generate a commit message and commit staged changes.

Steps

Check staged changes

git diff --cached --stat
git diff --cached

Check recent commit style
```
git log --oneline -10
```

Generate commit message following Conventional Commits:

Prefix	When to Use
`feat:`	New feature
`fix:`	Bug fix
`refactor:`	Code restructure, no behavior change
`docs:`	Documentation only
`test:`	Adding or fixing tests
`chore:`	Build, deps, config changes
`perf:`	Performance improvement
`style:`	Formatting, whitespace
`ci:`	CI/CD changes

Format rules
- Subject line: max 72 characters, imperative mood ("Add" not "Added")
- Body: wrap at 80 characters, explain WHY not WHAT
- If multiple changes: use bullet points in body

Commit

git commit -m "type: short description

- Detail 1
- Detail 2"

Show result
```
git log --oneline -1
```

Pre-Delivery Checklist

Before committing, verify:

git diff --cached was read (not just --stat)
Commit prefix matches the change type (feat/fix/refactor/etc.)
Subject line is under 72 characters
Subject uses imperative mood ("Add" not "Added")
No sensitive files staged (.env, credentials, keys)
No unrelated changes bundled in the same commit
Body explains WHY if the change is non-obvious

If nothing is staged

Run git status and tell the user what files are available to stage.

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 · 72 lines · 21 tokens per session scan A bd5bcf130fea

Subscribe to this mod's changes

commit is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (10 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 486 once invoked, about $0.0001 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 ai ai-coding anthropic claude claude-code-hooks

memstack-security-git-guard

Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…

cwinvestments/memstack · 92 tokens

github-workflow

GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.

Mindrally/skills · 23 tokens

git-workflow

Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.

Mindrally/skills · 23 tokens

lerna

Best practices for Lerna monorepo management, versioning, and publishing.

Mindrally/skills · 18 tokens

core-workflow

Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.

travisjneuman/.claude · 52 tokens

validate-changes

Evaluate staged changes using LLM-as-a-Judge before committing.

FlorianBruniaux/claude-code-ultimate-guide · 16 tokens