Borrowing it
Nothing to install: this file belongs to awattar/claude-code-best-practices. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/awattar/claude-code-best-practices/main/.claude/commands/commit.mdgit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWrote 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.
[](https://agentmods.dev/commands/awattar/claude-code-best-practices/commit)<a href="https://agentmods.dev/commands/awattar/claude-code-best-practices/commit"><img src="https://agentmods.dev/badge/commands/awattar/claude-code-best-practices/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.
<a href="https://agentmods.dev/commands/awattar/claude-code-best-practices/commit"><img src="https://agentmods.dev/badge/commands/awattar/claude-code-best-practices/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00524 |
| Opus 5.5 | $0.00004 | $0.00210 |
| Sonnet 5.5 | $0.00002 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00052 |
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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code User Command: Commit
This command helps you create well-formatted commits with conventional commit messages.
Usage
To create a commit, just type:
/commit
What This Command Does
- Checks which files are staged with
git status. - If 0 files are staged, automatically adds all modified and new files with
git add. - Performs a
git diffto understand what changes are being committed. - Analyzes the diff to determine if multiple related logical changes are present.
- If multiple related changes are detected, breaks the commit message into multiline message.
Agents Used
This command leverages two specialized agents for optimal results:
- general-code-quality-debugger - For analyzing code changes and ensuring commit quality
- general-technical-project-lead - For strategic decisions about commit structure and breaking changes
Each agent contributes expertise to ensure high-quality commits that follow best practices and maintain project standards.
Best Practices for Commits
IMPORTANT: The /commit command always follows standardized commit conventions and best practices. For detailed formatting rules and guidelines, refer to:
Commit Format Templates
- Format reference: @.gitmessage - Complete commit message format specification with examples
- Best practices: @.github/COMMIT_CONVENTION.md - Detailed guidelines for atomic commits, splitting commits, and workflow integration
Key Conventions
- Conventional commit format: Follows standardized format with issue linking
- Atomic commits: Each commit serves a single logical purpose
- Format enforcement: Automatic validation of commit message structure
- Issue integration: Automatic detection and formatting of GitHub issue references
Setup Git Template (Optional)
To use the commit message template with standard git commands:
git config commit.template .gitmessage
This will populate the commit message editor with the template format when using git commit without the -m flag.
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 · 62 lines · 11 tokens per session scan A a015a78b9401
commit is a command published in the GitHub repository awattar/claude-code-best-practices (262 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 524 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.