commit

A tool-guided way to create small Git commits that follow common commit-message rules. Git is the system developers use to track code changes.

In plain words
What is it for?
It is for committing a completed, focused change with an automatically generated intent, with an option to preserve already staged files.
Why use it?
It removes the need to write commit messages and stage changes manually for each focused update.

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

Made for: Claude Code, Codex.

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 388 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00041 $0.00388
Opus 5 $0.00020 $0.00194
Sonnet 5 $0.00008 $0.00078
Haiku 4.5 $0.00004 $0.00039

Measured yesterday against content hash 0224cc6ee141, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

Origin

This is a copy

88% identical to commit-and-push — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

git-agent/skills/commit/SKILL.md · 34 lines

What it actually says

CRITICAL:

  • Do NOT run git status, git diff, git log, or any other read commands before git-agent commit.
  • Execute git-agent commit directly. git-agent (v0.7.0+) automatically detects active model attribution from session environment variables (PI_MODEL, etc.).

Execution

  1. Derive a concise one-sentence intent from the conversation or $ARGUMENTS.
  2. Pass --co-author "<co-author>" if explicitly specified in $ARGUMENTS or user instructions.
  3. Run primary commit command:
    git-agent commit --intent "<intent>"
    
  4. If specific files are already staged, pass --no-stage:
    git-agent commit --no-stage --intent "<intent>"
    
  5. On auth error (401), retry with --free:
    git-agent commit --free --intent "<intent>"
    
  6. Fallback (if git-agent binary is not found): report the error and ask the user to install git-agent or run git commands manually.

CLI Reference: ../../references/cli.md

Deterministic messages: When an exact commit message is required (e.g. version bump chore: bump version to 0.11.0), pass the full conventional message as the --intent value. The intent is used as the commit subject verbatim.

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 · 34 lines · 41 tokens per session scan A 0224cc6ee141

Subscribe to this mod's changes

commit is a skill published in the GitHub repository FradSer/dotclaude (587 stars, last pushed 20d ago), licensed MIT. It adds 41 tokens to every session and 388 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to commit-and-push, differing in 9 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens