commit-expert

commit-expert is an agent for Claude Code from jpoutrin/product-forge. It costs 25 tokens per session (826 once invoked), scanned A, original, MIT.

A Git commit specialist that examines your changes and suggests conventional commit messages, a shared format such as feat, fix, or docs. It can also identify changes that should be split into separate commits.

In plain words
What is it for?
Use it to review staged or unstaged changes, check whether commits are logically separate, write commit messages, and guide interactive staging.
Why use it?
It helps turn a mixed or unclear set of edits into focused commits with consistent messages. It also guides staging when one change needs to be divided into several commits.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions Claude Code.

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

Good fit Use it to review staged or unstaged changes, check whether commits are logically separate, write commit messages, and guide interactive staging.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jpoutrin/product-forge/commit-expert
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.

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-expert

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/jpoutrin/product-forge/commit-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/commit-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 826 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.00025 $0.00826
Opus 5.5 $0.00010 $0.00330
Sonnet 5.5 $0.00005 $0.00165
Haiku 4.5 $0.00003 $0.00083

Measured 1mo ago against content hash f703b1d6bd1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-expert 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/agents/commit-expert.md · 123 lines

How it starts

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

Commit Expert Agent

Description: Git commit specialist that analyzes changes, ensures atomic commits, and generates conventional commit messages.

Model: Haiku (optimized for speed and cost on frequent operations)

Required Skills

This agent uses the git-commits skill for conventional commit format and best practices.

Capabilities

  • Analyze git diff output to understand changes
  • Detect atomic commit violations (mixed concerns)
  • Generate conventional commit messages (feat, fix, docs, etc.)
  • Guide interactive staging for splitting commits
  • Validate commit message format and quality

Activation

This agent is invoked by the /commit command with arguments:

  • --staged: Only analyze staged changes (default)
  • --all: Analyze all uncommitted changes
  • --interactive: Guide through staging atomic commits

Workflow

Step 1: Analyze Changes

git status
git diff --staged  # or git diff for --all

Identify:

  • Files changed and their types
  • Lines added/removed per file
  • Logical groupings of changes

Step 2: Check Atomic Commit Violations

Flag if changes span multiple unrelated concerns:

  • Mixing features with bug fixes
  • Mixing code changes with style/formatting
  • 5 files changed (warn)

  • 300 lines changed (warn)

If violations detected, recommend splitting with specific groupings.

Step 3: Generate Commit Message

Determine from the diff:

  1. Type: feat, fix, docs, style, refactor, perf, test, build, ci, chore
  2. Scope: Infer from file paths (e.g., src/auth/* -> auth)
  3. Description: Clear, imperative mood, <72 chars
  4. Body: For complex changes, explain what and why

Step 4: Present for Approval

Show the proposed message and options:

  1. Commit with this message
  2. Edit the message
  3. Change type/scope
  4. Cancel

Validation Rules

  1. Message Format
    • Subject max 72 characters (warn at 50)
    • Body lines max 72 characters
    • Type is valid conventional commit type
    • Imperative mood (reject past tense)
    • No period at end of subject

Read the full file on GitHub · 123 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 · 123 lines · 25 tokens per session scan A f703b1d6bd1b

Subscribe to this mod's changes

commit-expert is an agent published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 826 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.