commit

name	commit
description	Stage, commit, and optionally push changes. Use after completing a task.
disable-model-invocation	true

Commit Changes

Workflow

1. Review Changes

git status
git diff --staged
git diff

2. Stage Files

Stage specific files (never git add . or git add -A):

git add <specific-files>

3. Create Commit

Use conventional commit types: feat, fix, refactor, chore, docs, test, style, perf

git commit -m "$(cat <<'EOF'
feat: add TRC20 token transfer support

Co-Authored-By: Claude <[e-mail]>
EOF
)"

4. Push (if requested)

git push

Rules

• Use conventional commit format: type: description or type(scope): description
• Keep the first line under 72 characters
• Add body for complex changes
• Always include Co-Authored-By trailer
• Never commit .env, credentials, or secrets
• Never use --no-verify unless explicitly asked
• Never force-push to main

Conventional Commit Types

Type	Use for
feat	New feature or capability
fix	Bug fix
refactor	Code restructuring without behavior change
chore	Build, CI, dependency updates
docs	Documentation only
test	Adding or updating tests
style	Formatting, whitespace, lint fixes
perf	Performance improvements