A command that creates a git commit with a conventional commit message based on the staged changes, recent commit style, and the purpose of the work.

Use it when staged changes are ready to commit and you want an automatically generated, concise conventional commit message.

It avoids vague or inconsistent commit messages by checking what is staged and choosing a standard type such as feature, fix, documentation, or test.

commit — Command by CloudAI-X

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/cloudai-x/opencode-workflow/commit

Clone the repo

git clone --depth 1 https://github.com/CloudAI-X/opencode-workflow

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

When invoked 461 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.00009	$0.00461
Opus 5	$0.00005	$0.00230
Sonnet 5	$0.00002	$0.00092
Haiku 4.5	$0.00001	$0.00046

Measured 2d ago against content hash 1f6590fc7a7d, 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 2d 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 · 73 lines

What it actually says

Git Commit Command

Create a well-structured git commit by analyzing staged changes and generating a conventional commit message.

Phase 1: Gather Context

Run these commands in parallel to understand the current state:

git status - See all staged and unstaged changes
git diff --cached - View the actual staged changes that will be committed
git log --oneline -5 - Review recent commit message style for consistency

Phase 2: Analyze Changes

Based on the staged diff, determine:

Change Type (use conventional commits):
- feat: New feature
- fix: Bug fix
- refactor: Code restructuring without behavior change
- docs: Documentation only
- test: Adding or updating tests
- chore: Maintenance tasks
- style: Formatting, whitespace
- perf: Performance improvement
- ci: CI/CD changes
Scope (optional): Affected module or component
Description: Concise summary focusing on WHY, not WHAT

Phase 3: Generate Commit Message

Format: type(scope): description

Rules:

Use imperative mood ("Add feature" not "Added feature")
Keep first line under 72 characters
Focus on the purpose and impact
Add body for complex changes explaining reasoning

Phase 4: Execute Commit

If there are unstaged changes that should be included, ask user first
Stage any additional files if requested
Execute the commit with the generated message
Run git status to verify success

Output Format

Commit Analysis
---------------
Type: [type]
Scope: [scope or "none"]
Files: [number] files changed

Generated Message:
[commit message]

Commit Status: [success/failure]

Safety Checks

NEVER commit files that appear to contain secrets (.env, credentials, API keys)
WARN if committing lock files or large binary files
CONFIRM before committing if there are untracked files that might be forgotten

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.

2d ago First seen · 73 lines · 9 tokens per session scan A 1f6590fc7a7d

Subscribe to this mod's changes

commit is a command published in the GitHub repository CloudAI-X/opencode-workflow (274 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 461 once invoked, about $0.0000 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-30.

Git and workflow

commit

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Git Commit Command

Phase 1: Gather Context

Phase 2: Analyze Changes

Phase 3: Generate Commit Message

Phase 4: Execute Commit

Output Format

Safety Checks

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement