commit-message-generator

commit-message-generator is a skill for Claude Code, Codex from armanzeroeight/fastagent-plugins. It costs 31 tokens per session (1,326 once invoked), scanned A, original, MIT.

A guide that reads Git changes and suggests a conventional commit message, a standard format that labels changes such as features, fixes, tests, and documentation.

In plain words
What is it for?
Use it to inspect staged changes, choose a commit type and scope, and write a concise message describing the change.
Why use it?
It makes commit history clearer and helps teams follow the same naming convention when recording changes.

Skill for Claude CodeCodex

Part of the git-workflow-toolkit plugin — 2 skills shipped together

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/armanzeroeight/fastagent-plugins/commit-message-generator
Any agent
npx skills add armanzeroeight/fastagent-plugins --skill commit-message-generator
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Made for: Claude Code, Codex.

Or install git-workflow-toolkit, the plugin that ships this one along with the rest of its 2 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 commit-message-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/commit-message-generator.svg)](https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/commit-message-generator)
Your own site
<a href="https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/commit-message-generator"><img src="https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/commit-message-generator.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00031 $0.01326
Opus 5 $0.00015 $0.00663
Sonnet 5 $0.00006 $0.00265
Haiku 4.5 $0.00003 $0.00133

Measured yesterday against content hash 336db188baee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit-message-generator 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.

plugins/git-workflow-toolkit/skills/commit-message-generator/SKILL.md · 284 lines

How it starts

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

Commit Message Generator

Generate clear, conventional commit messages from git diffs.

Quick Start

Analyze staged changes and generate message:

git diff --staged
# Then generate message following conventional commits format

Instructions

Step 1: Analyze Changes

Review the git diff to understand:

  • What files changed
  • What functionality was added/modified/removed
  • Scope of changes (component, module, feature)
  • Breaking changes or deprecations
git diff --staged
# or for specific files
git diff --staged path/to/file

Step 2: Determine Commit Type

feat: New feature

  • Adding new functionality
  • New user-facing capability
  • New API endpoint

fix: Bug fix

  • Fixing a bug
  • Correcting behavior
  • Resolving an issue

docs: Documentation

  • README updates
  • Code comments
  • API documentation

style: Code style

  • Formatting changes
  • Missing semicolons
  • Whitespace changes
  • No code logic changes

refactor: Code refactoring

  • Restructuring code
  • No functionality change
  • Performance improvements

test: Tests

  • Adding tests
  • Updating tests
  • Test infrastructure

chore: Maintenance

  • Dependency updates
  • Build configuration
  • CI/CD changes
  • Tooling updates

perf: Performance

  • Performance improvements
  • Optimization changes

ci: CI/CD

  • CI configuration
  • Build scripts
  • Deployment changes

build: Build system

  • Build tool changes
  • External dependencies

revert: Revert

  • Reverting previous commit

Step 3: Identify Scope

Scope indicates what part of codebase changed:

  • Component name: (button), (navbar)
  • Module name: (auth), (api)
  • Feature area: (payments), (search)
  • Package name: (core), (utils)

Optional but recommended for clarity.

Step 4: Write Description

Subject line (first line):

  • Use imperative mood ("add" not "added")
  • No period at end
  • Max 50-72 characters
  • Lowercase after type
  • Clear and concise

Body (optional, after blank line):

  • Explain what and why, not how
  • Wrap at 72 characters
  • Use bullet points for multiple changes
  • Reference issues/tickets

Read the full file on GitHub · 284 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. yesterday First seen · 284 lines · 31 tokens per session scan A 336db188baee

Subscribe to this mod's changes

commit-message-generator is a skill published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,326 once invoked, about $0.0002 per session on Opus 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.

Related

Other skills, from other repositories

git-github-workflow

处理基于 git 和 GitHub 的真实协作工作流。当任务涉及仓库同步、分支管理、修复 bug、提交代码、创建或更新 PR、处理 review、解决冲突、检查 GitHub 认证与权限、或需要通过 fork 与用户仓库协作时使用,强调安全、干净、可审计的协作流程。必须在需要时使用该 Skill 并严格遵守相关规范!!!

KroMiose/nekro-agent · 101 tokens

build-monetized-app

Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…

elizaOS/eliza · 126 tokens

contribute-to-eliza

Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…

elizaOS/eliza · 68 tokens

discord

Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…

elizaOS/eliza · 70 tokens

eliza-cloud-buy-domain

Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…

elizaOS/eliza · 125 tokens

tmux

Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…

elizaOS/eliza · 87 tokens