commit

commit is a skill for Claude Code from jpoutrin/product-forge. It costs 14 tokens per session (2,077 once invoked), scanned A, original, MIT.

A guided Git commit helper that reviews your changes, checks whether they belong together, and writes a conventional commit message. Git is the tool developers use to track code changes.

In plain words
What is it for?
Use it to inspect staged or unstaged changes, split unrelated work into atomic commits, and create consistently formatted commit messages.
Why use it?
It helps avoid vague commit messages and commits that mix unrelated work, making project history easier to understand.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Part of the git-workflow plugin — 11 skills, 8 agents shipped together

Good fit Use it to inspect staged or unstaged changes, split unrelated work into atomic commits, and create consistently formatted commit messages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpoutrin/product-forge/commit
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 jpoutrin/product-forge --skill commit
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

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

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 commit

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/commit"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,077 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.00014 $0.02077
Opus 5.5 $0.00006 $0.00831
Sonnet 5.5 $0.00003 $0.00415
Haiku 4.5 $0.00001 $0.00208

Measured 1mo ago against content hash 14f599507348, 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 · 357 lines

How it starts

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

commit

Category: Development

Usage

commit [--all | --staged | --interactive]

Arguments

  • --all: Analyze all uncommitted changes (staged + unstaged)
  • --staged: Only analyze currently staged changes (default)
  • --interactive: Guide through staging changes atomically before committing

Execution Method

This command delegates to the commit-expert agent (Haiku model) for fast, cost-effective execution.

Delegation: Use the Task tool with:

  • subagent_type: "git-workflow:commit-expert"
  • prompt: Include the mode (--staged, --all, or --interactive) and current working directory

Example:

Task(subagent_type="git-workflow:commit-expert", prompt="Run commit in --staged mode in /path/to/repo")

Execution Instructions for Claude Code

When this command is run, Claude Code should:

  1. Analyze Changes

    • Run git status to understand current state
    • Run git diff --staged for staged changes (or git diff for all)
    • Identify the files and types of changes
  2. Check for Atomic Commit Violations

    • Flag if changes span multiple unrelated concerns
    • Warn if mixing features, fixes, refactoring, and style changes
    • Suggest splitting if commit is too large (>300 lines)
  3. Generate Commit Message

    • Determine appropriate type (feat, fix, docs, etc.)
    • Identify scope from file paths
    • Write clear, imperative description
    • Add body if changes are complex
  4. Present for Approval

    • Show the proposed commit message
    • Allow editing before committing
    • Execute the commit

Interactive Flow

Step 1: Analyze Changes

🔍 Analyzing your changes...

Staged changes:
  M  src/auth/login.py (+45, -12)
  M  src/auth/tokens.py (+23, -5)
  A  tests/test_login.py (+89)

Unstaged changes:
  M  src/styles/button.css (+15, -3)
  M  README.md (+20)

Step 2: Atomic Commit Check

✅ Good: Changes appear to be a single logical unit
   All changes relate to authentication/login functionality

   OR

⚠️  Warning: Changes may not be atomic

   These appear to be separate concerns:
   1. Authentication changes (src/auth/*)
   2. Style changes (src/styles/button.css)
   3. Documentation (README.md)

   Recommendations:
   - Commit auth changes first: feat(auth): ...
   - Commit style changes: fix(ui): ...
   - Commit docs separately: docs: ...

   Would you like to:
   1. Proceed with current staging (not recommended)
   2. Unstage some files and commit in parts
   3. Show me how to split this commit

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

  1. 1mo ago First seen · 357 lines · 14 tokens per session scan A 14f599507348

Subscribe to this mod's changes

commit is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 2,077 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-09-03.