A command for creating Git commits in a consistent format, using a change type, optional scope, emoji, and subject.

Use it after making code changes to record features, fixes, documentation, tests, maintenance, and other updates with correctly formatted commit messages.

It removes the need to remember the project's commit-message rules and helps keep its history uniform.

How AmitGurbani/mcp-server-woocommerce configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AmitGurbani/mcp-server-woocommerce. 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/AmitGurbani/mcp-server-woocommerce/main/.claude/commands/commit.md

Clone the repo

git clone --depth 1 https://github.com/AmitGurbani/mcp-server-woocommerce

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/amitgurbani/mcp-server-woocommerce/commit/github.svg)](https://agentmods.dev/commands/amitgurbani/mcp-server-woocommerce/commit)

Your own site

<a href="https://agentmods.dev/commands/amitgurbani/mcp-server-woocommerce/commit"><img src="https://agentmods.dev/badge/commands/amitgurbani/mcp-server-woocommerce/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/amitgurbani/mcp-server-woocommerce/commit"><img src="https://agentmods.dev/badge/commands/amitgurbani/mcp-server-woocommerce/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 751 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.00007	$0.00751
Opus 5.5	$0.00003	$0.00300
Sonnet 5.5	$0.00001	$0.00150
Haiku 4.5	$0.00001	$0.00075

Measured 2mo ago against content hash 9348a2e61473, 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 2mo 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.

.claude/commands/commit.md · 102 lines

How it starts

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

Create a git commit following the project's conventional commit format with emoji prefixes.

Commit Message Format

<type>(<scope>): <emoji> <subject>

[optional body]

[optional footer]

Types and Emojis

feat: ✨ New feature
fix: 🐛 Bug fix
docs: 📝 Documentation changes
style: 💄 Code style/formatting (no logic changes)
refactor: ♻️ Code refactoring
perf: ⚡ Performance improvements
test: ✅ Adding or updating tests
chore: 🔧 Maintenance tasks, dependencies
ci: 👷 CI/CD changes
build: 📦 Build system changes
revert: ⏪ Revert previous commit

Scopes

Common scopes in this project:

tools - MCP tool files (products, orders, categories, etc.)
services - Base service layer, WooCommerce client
server - Server setup, entry point
config - tsconfig, package.json, .mcp.json
deps - Dependency updates

CRITICAL: No Attribution in Commits

DO NOT add any Claude Code attribution to commit messages.

Commit messages must be clean and end after the optional body/footer. Never include:

❌ "Generated with Claude Code"
❌ "Co-Authored-By: Claude"
❌ Links to claude.com
❌ Any other attribution lines

The commit message should contain ONLY:

✅ Type, scope, emoji, and subject line
✅ Optional body explaining "why"
✅ Optional footer (issue references, breaking changes)

Instructions

Run git status to see what files are staged/modified
Run git diff --staged to review staged changes
Run git log --oneline -10 to see recent commit style
Analyze the changes and determine:
- Type (feat, fix, docs, etc.)
- Scope (which area affected)
- Clear, concise subject line (50 chars max)
- Body if needed to explain "why" not "what"
Stage any unstaged files that should be included: git add <files>
Create the commit with proper format (NO ATTRIBUTION!)
Run git status after committing to confirm

Examples

# New MCP tool
git commit -m "feat(tools): ✨ add product variation tools"

# Bug fix in service layer
git commit -m "fix(services): 🐛 handle WooCommerce API timeout errors"

# Documentation update
git commit -m "docs(config): 📝 update CLAUDE.md with new tools"

# Dependency upgrade
git commit -m "chore(deps): ⬆️ upgrade zod to v4"

# Refactoring
git commit -m "refactor(services): ♻️ extract pagination logic to helper"

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

2mo ago First seen · 102 lines · 7 tokens per session scan A 9348a2e61473

Subscribe to this mod's changes

commit is a command published in the GitHub repository AmitGurbani/mcp-server-woocommerce (2 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 751 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-31.

Commits Git and workflow ai-tools mcp mcp-server model-context-protocol woocommerce

mcp-server-woocommerce: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Commit Message Format

Types and Emojis

Scopes

CRITICAL: No Attribution in Commits

Instructions

Examples

What this file has done since we first saw it

Other commands, from other repositories

fest-commit

merge

template

umt-doctor

umt

commit