A procedure for committing changes to Git, the system that records code history. It covers checking recent commits and current changes, selecting files, writing an English Conventional Commit message, and verifying the result.

Reviewing changes, staging the right files, creating well-formed commits, and confirming that a commit was created.

It reduces mistakes in the commit process and keeps the project history clear and consistent.

How j5ik2o/okite-ai configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to j5ik2o/okite-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/j5ik2o/okite-ai/main/.agents/commands/git-commit.md

Clone the repo

git clone --depth 1 https://github.com/j5ik2o/okite-ai

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/j5ik2o/okite-ai/git-commit/github.svg)](https://agentmods.dev/commands/j5ik2o/okite-ai/git-commit)

Your own site

<a href="https://agentmods.dev/commands/j5ik2o/okite-ai/git-commit"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/git-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/j5ik2o/okite-ai/git-commit"><img src="https://agentmods.dev/badge/commands/j5ik2o/okite-ai/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.00528
Opus 5.5	$0.00006	$0.00211
Sonnet 5.5	$0.00003	$0.00106
Haiku 4.5	$0.00001	$0.00053

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

Security

Grade A, and why

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

Copies of this mod

1 near-identical copy found in the catalogue:

git-commit — 100% identical, 0 lines differ

.agents/commands/git-commit.md · 57 lines

What it actually says

意味のある変更単位ごとにコミットを行うことは、コードの履歴を明確にし、将来の変更を追跡しやすくするために重要です。

以下の手順に従って、ワーキングディレクトリでの変更をコミットします。

0. 直近のコミットを確認する

直近にてどのようにコミットされているかを確認する

git log --oneline

これにより、最近のコミットの一覧が表示され、コミットメッセージとハッシュが確認できます。

1. 変更を確認する

まず、現在のワーキングディレクトリでの変更を確認します。以下のコマンドを実行してください：

git status

2. 変更をステージングする

変更をコミットする前に、ステージングエリアに追加する必要があります。以下のコマンドを使用して、すべての変更をステージングします：

git add 対象ファイルやディレクトリ

意味のある変更単位ごとにファイルを指定すること。無条件にすべての変更を追加しないでください。

3. コミットメッセージを作成する

コミットメッセージは、変更内容を簡潔に説明する重要な部分です。以下のコマンドを使用して、コミットを作成します：

git commit -m "コミットメッセージをここに入力"

コミットメッセージはConventional Commitsに従い、英語で記述してください。
co-authorやコミットメッセージに"Claude Code"などのエージェント名は含めないこと。

4. コミットを確認する

コミットが正しく行われたかを確認するために、以下のコマンドを実行します：

git log --oneline

これにより、最近のコミットの一覧が表示され、コミットメッセージとハッシュが確認できます。

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 · 57 lines · 14 tokens per session scan A f104e8245ea0

Subscribe to this mod's changes

git-commit is a command published in the GitHub repository j5ik2o/okite-ai (80 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 528 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-01.

Commits Git and workflow

okite-ai: Command for Claude Code