A command for creating a Git commit, which is a saved set of code changes, using the Conventional Commits format. It reviews the changes, chooses a commit category, writes the message, stages files, and commits them.

Use it to inspect changed files, choose labels such as feature or bug fix, write a structured message, stage changes, and create the commit.

It turns unfinished or inconsistently described changes into a clear project history that tools and teammates can understand.

commit — Command for coding agents by boparaiamrit: A command for creating a Git commit, which is…

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 commands/boparaiamrit/skills-by-amrit/commit

Clone the repo

git clone --depth 1 https://github.com/boparaiamrit/skills-by-amrit

Or install skills-by-amrit, the plugin that ships this one along with the rest of its 33 skills, 34 commands, 9 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/commit.svg)](https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/commit)

Your own site

<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/commit"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/commit.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 403 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00403
Opus 5	$0.00006	$0.00201
Sonnet 5	$0.00003	$0.00081
Haiku 4.5	$0.00001	$0.00040

Measured 4d ago against content hash f53da5f7c81b, 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 4d 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.

commands/commit.md · 52 lines

What it actually says

/commit — Smart Commit

Create a well-formatted commit message following Conventional Commits.

Instructions

Check what changed:
- Run git status and git diff --staged
- If nothing is staged, run git diff to see unstaged changes
- Summarize the changes in your mind before writing the message
Determine commit type:
- feat: — New feature or capability
- fix: — Bug fix
- refactor: — Code change that neither fixes a bug nor adds a feature
- docs: — Documentation only
- test: — Adding or updating tests
- chore: — Maintenance tasks, dependency updates
- perf: — Performance improvement
- ci: — CI/CD changes
- style: — Formatting, whitespace (no logic change)

Write the commit message:

<type>(<scope>): <short description>

<body — explain WHAT and WHY, not HOW>

<footer — breaking changes, issue references>

Rules:
- Subject line ≤ 72 characters
- Use imperative mood ("add", not "added" or "adds")
- Scope from $ARGUMENTS if provided, otherwise infer from changed files
- Body should explain WHY the change was made
- Reference issues if applicable: Fixes #123
Stage and commit:
- Stage all relevant files (ask user if unsure)
- Create the commit with the formatted message
- Show the commit hash and summary
Do NOT push — let the user decide when to push.

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.

4d ago First seen · 52 lines · 13 tokens per session scan A f53da5f7c81b

Subscribe to this mod's changes

commit is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 403 once invoked, about $0.0001 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-08-31.

Commits Git and workflow

commit

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/commit — Smart Commit

Instructions

What this file has done since we first saw it

Other commands, from other repositories

cr

standup

git

commit-claude-config

commit

session-report