A command that prepares Git commits with conventional commit messages and emoji, after checking the project and reviewing the changes.

Use it to stage modified files, run pre-commit checks, determine the change type, create a commit, and push it.

It reduces the manual work of staging files, checking pre-commit validation, understanding the diff, and writing a consistent commit message. It also specifies that commits should be pushed.

commit — Command for Claude Code by jjmartres/ai-coding-agents

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/jjmartres/ai-coding-agents

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jjmartres/ai-coding-agents/commit/github.svg)](https://agentmods.dev/commands/jjmartres/ai-coding-agents/commit)

Your own site

<a href="https://agentmods.dev/commands/jjmartres/ai-coding-agents/commit"><img src="https://agentmods.dev/badge/commands/jjmartres/ai-coding-agents/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jjmartres/ai-coding-agents/commit"><img src="https://agentmods.dev/badge/commands/jjmartres/ai-coding-agents/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,873 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 97% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00011	$0.01873
Opus 5.5	$0.00004	$0.00749
Sonnet 5.5	$0.00002	$0.00375
Haiku 4.5	$0.00001	$0.00187

Measured 1mo ago against content hash 0e954c4ba42d, 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.

Origin

This is a copy

97% identical to commit — 20 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.

shared/.ai-agents/commands/commit.md · 159 lines

How it starts

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

Commit Command

You are an AI agent that helps create well-formatted git commits with conventional commit messages and emoji icons, follow these instructions exactly. Always run and push the commit, you don't need to ask for confirmation unless there is a big issue or error.

Prefer to explain WHY something was done from an end user perspective instead of WHAT was done.

Instructions for Agent

When the user runs this command, execute the following workflow:

Check command mode:
- If user you have $ARGUMENTS which is simple, skip to step 3
Run pre-commit validation:
- Execute pre-commit run -a and report any issues
- If fails, ask user if they want to proceed anyway or fix issues first
Analyze git status:
- Run git status --porcelain to check for changes
- If no files are staged, run git add . to stage all modified files
- If files are already staged, proceed with only those files
Analyze the changes:
- Run git diff --cached to see what will be committed
- Analyze the diff to determine the primary change type (feat, fix, docs, etc.)
- Identify the main scope and purpose of the changes
Generate commit message:
- Choose appropriate emoji and type from the reference below
- Create message following format: <emoji> <type>: <description>
- Keep description concise, clear, and in imperative mood
- Show the proposed message to user for confirmation
Execute the commit:
- Run git commit -m "<generated message>"
- Display the commit hash and confirm success
- Provide brief summary of what was committed

Commit Message Guidelines

When generating commit messages, follow these rules:

Atomic commits: Each commit should contain related changes that serve a single purpose
Imperative mood: Write as commands (e.g., "add feature" not "added feature")
Concise first line: Keep under 72 characters
Conventional format: Use <emoji> <type>: <description> where type is one of:
- feat: A new feature
- fix: A bug fix
- docs: Documentation changes
- style: Code style changes (formatting, etc.)
- refactor: Code changes that neither fix bugs nor add features
- perf: Performance improvements
- test: Adding or fixing tests
- chore: Changes to the build process, tools, etc.
Present tense, imperative mood: Write commit messages as commands (e.g., "add feature" not "added feature")
Concise first line: Keep the first line under 72 characters
Emoji: Each commit type is paired with an appropriate emoji:
- ✨ feat: New feature
- 🐛 fix: Bug fix
- 📝 docs: Documentation
- 💄 style: Formatting/style
- ♻️ refactor: Code refactoring
- ⚡️ perf: Performance improvements
- ✅ test: Tests
- 🔧 chore: Tooling, configuration
- 🚀 ci: CI/CD improvements
- 🗑️ revert: Reverting changes
- 🧪 test: Add a failing test
- 🚨 fix: Fix compiler/linter warnings
- 🔒️ fix: Fix security issues
- 👥 chore: Add or update contributors
- 🚚 refactor: Move or rename resources
- 🏗️ refactor: Make architectural changes
- 🔀 chore: Merge branches
- 📦️ chore: Add or update compiled files or packages
- ➕ chore: Add a dependency
- ➖ chore: Remove a dependency
- 🌱 chore: Add or update seed files
- 🧑‍💻 chore: Improve developer experience
- 🧵 feat: Add or update code related to multithreading or concurrency
- 🔍️ feat: Improve SEO
- 🏷️ feat: Add or update types
- 💬 feat: Add or update text and literals
- 🌐 feat: Internationalization and localization
- 👔 feat: Add or update business logic
- 📱 feat: Work on responsive design
- 🚸 feat: Improve user experience / usability
- 🩹 fix: Simple fix for a non-critical issue
- 🥅 fix: Catch errors
- 👽️ fix: Update code due to external API changes
- 🔥 fix: Remove code or files
- 🎨 style: Improve structure/format of the code
- 🚑️ fix: Critical hotfix
- 🎉 chore: Begin a project
- 🔖 chore: Release/Version tags
- 🚧 wip: Work in progress
- 💚 fix: Fix CI build
- 📌 chore: Pin dependencies to specific versions
- 👷 ci: Add or update CI build system
- 📈 feat: Add or update analytics or tracking code
- ✏️ fix: Fix typos
- ⏪️ revert: Revert changes
- 📄 chore: Add or update license
- 💥 feat: Introduce breaking changes
- 🍱 assets: Add or update assets
- ♿️ feat: Improve accessibility
- 💡 docs: Add or update comments in source code
- 🗃️ db: Perform database related changes
- 🔊 feat: Add or update logs
- 🔇 fix: Remove logs
- 🤡 test: Mock things
- 🥚 feat: Add or update an easter egg
- 🙈 chore: Add or update .gitignore file
- 📸 test: Add or update snapshots
- ⚗️ experiment: Perform experiments
- 🚩 feat: Add, update, or remove feature flags
- 💫 ui: Add or update animations and transitions
- ⚰️ refactor: Remove dead code
- 🦺 feat: Add or update code related to validation
- ✈️ feat: Improve offline support

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

1mo ago First seen · 159 lines · 11 tokens per session scan A 0e954c4ba42d

Subscribe to this mod's changes

commit is a command published in the GitHub repository jjmartres/ai-coding-agents (49 stars, last pushed 8d ago), licensed MIT. It adds 11 tokens to every session and 1,873 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to commit, differing in 20 lines, and is treated as a copy.

Claude Code Commits Git and workflow agents agentskills claude-skills configuration dotfiles

commit

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Commit Command

Instructions for Agent

Commit Message Guidelines

What this file has done since we first saw it

Other commands, from other repositories

make-pr

ship

remove-deadcode

commit

genshijin-commit

quick-commit