agentmods.dev

git-commit

git-commit is a skill for Claude Code from mgiovani/cc-arsenal. It costs 69 tokens per session (813 once invoked), scanned A, original, MIT.

A workflow that examines a Git change and creates a Conventional Commits-style commit message before committing it. Conventional Commits are a shared format such as feat, fix, or docs followed by a short description.

In plain words
What is it for?
Use it when staging changes, creating a commit, or generating a commit message from the current Git diff.
Why use it?
It ties the commit message to the actual diff and checks linting first, making project history more consistent and reviewable.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cc-arsenal-git plugin — 6 skills shipped together , and of cc-arsenal

not rated 8repo changed 22d ago A scan 69 tokens original MIT

Good fit Use it when staging changes, creating a commit, or generating a commit message from the current Git diff.

Compare 6 skills from other repositories ↓
View source ↗ mgiovani/cc-arsenal
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add mgiovani/cc-arsenal
Claude Code
/plugin install cc-arsenal-git

Made for: Claude Code.

Or install cc-arsenal-git, the plugin that ships this one along with the rest of its 6 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.

agentmods badge for git-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/git-commit/github.svg)](https://agentmods.dev/skills/mgiovani/cc-arsenal/git-commit)
Your own site
<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/git-commit"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/git-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.

agentmods 80×15 button for git-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/git-commit"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 813 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.00069 $0.00813
Opus 5.5 $0.00028 $0.00325
Sonnet 5.5 $0.00014 $0.00163
Haiku 4.5 $0.00007 $0.00081

Measured 22d ago against content hash 770ce36ded9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-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 22d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/pre-commit-lint.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/git-commit/SKILL.md · 81 lines

How it starts

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

Git Commit

Generate a conventional commit message and create the commit.

Quality Guidelines

Base the message only on what the diff actually shows, not assumptions:

  1. Read git status and git diff --staged (or git diff if nothing is staged yet) before writing anything.
  2. Check which files/modules changed before setting scope.
  3. Look for removed exports, changed signatures, deleted functions to catch breaking changes.
  4. If the purpose of a change is unclear, ask the user rather than guess.

Pre-commit Linting

In Claude Code, a PreToolUse hook runs before every git commit: it detects the project's linter (Node's npm/bun/pnpm/yarn run lint, Python's ruff/flake8, make lint, rubocop, golangci-lint) and blocks the commit if it fails. No linter configured means the commit proceeds unblocked. Outside Claude Code (no hook support), run the project's lint command yourself before committing. Never bypass a failing lint with --no-verify: fix the errors and re-run the commit instead.

Workflow

  1. Run git status and git diff --staged to see what actually changed.
  2. If the diff mixes unrelated concerns (e.g. a feature plus an unrelated fix plus docs), split into separate commits by staging each group with git add <files> and committing them one at a time. Otherwise, one commit is enough, don't force a split.
  3. For each commit, pick the type:
    • feat: new feature
    • fix: bug fix
    • docs: documentation only
    • style: formatting, no code meaning change
    • refactor: neither fixes a bug nor adds a feature
    • perf: performance improvement
    • test: adding or correcting tests
    • build: build system or dependency changes
    • ci: CI configuration/scripts
    • chore: everything else that doesn't touch src or tests
    • revert: reverts a previous commit
  4. Format as type(scope): description, scope optional, description imperative mood ("add" not "added"), max ~50 characters. Skip the body for a typo fix or a single dependency bump; add a wrapped body (why, not how) once the change alters behavior or touches multiple files. For breaking changes, append ! after the scope and add a BREAKING CHANGE: ... footer.

Read the full file on GitHub · 81 lines

Files

What ships with it

3 files 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. 22d ago Changed · -5 lines 770ce36ded9c
  2. 1mo ago Changed · +1 lines 8f9b2f369436
  3. 1mo ago First seen · 85 lines · 69 tokens per session scan A f32f88118f28

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository mgiovani/cc-arsenal (8 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 813 once invoked, about $0.0003 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 CodeCommitsGit and workflowagent-skillsagentskillsai-agentsautomationcli
Related

Other skills, from other repositories

autofix-pr

Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…

QwenLM/qwen-code · 123 tokens

cw-land

Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.

Hmbown/Codewhale · 44 tokens

git-commit

Analyze changes with Git only and auto-generate conventional commit messages with optional emoji; suggests splitting commits when needed, runs local Git hooks by default (use --no-verify to skip).

UfoMiao/zcf · 41 tokens

git-master

MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog). Load it before running git yourself, or pass loadskills=['git-master'] to the task that commits. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.

code-yeongyu/lazycodex · 93 tokens

atmos-git

Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims and hook env vars, pre-commit framework migration, Starlark git.sandbox checks and unstaged fixes, signed commits, managed workdirs, fork-PR trust gate (clone gate and posting gate), and auth via identities or…

cloudposse/atmos · 82 tokens

conventional-commit

Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.

termio-sh/termio · 47 tokens