git commit tool

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git...

Security Scan

The skill's requirements and instructions match its stated purpose (creating conventional commits) and it makes no disproportionate requests, but the AI-GEN footer requirement and enforced language are implementation/operational quirks to be aware of.

Purpose & Capability

Name and description (git commit / conventional commits) align with the instructions: the SKILL.md only uses git commands (git diff, git status, git add, git commit) and staging guidance which are appropriate and expected for this purpose.

Instruction Scope

Instructions stay within commit-related actions and explicitly forbid destructive or unrelated behavior (no config edits, no force pushes, avoid secrets). However, the SKILL.md requires commit messages in Simplified Chinese and mandates an "AI-GEN" footer that includes a model name and a percentage/line count of AI-generated code. The skill does not explain how to compute or obtain the model name/AI percentage—this is ambiguous and may produce inaccurate or privacy-leaking metadata in commits.

Install Mechanism

Instruction-only skill with no install steps, code files, or external downloads. Lowest-risk install profile.

Credentials

No environment variables, credentials, or config paths are requested. The operations performed (git commands) are proportional to the stated goal.

Persistence & Privilege

always is false, and there is no request to modify other skills or system-wide settings. The skill runs commands locally via Bash when invoked and does not request elevated persistence.

Assessment

This skill appears coherent for its purpose: it runs git commands to create conventional commits. Before installing or using it, consider: (1) the skill will run git commands that modify your repository—review diffs and staged files before committing; (2) the SKILL.md enforces commit messages in Simplified Chinese—ensure that's what you want; (3) it requires adding an "AI-GEN" footer with model name and AI-generated percentage/line counts — the skill doesn't explain how to compute these or where to obtain the model name, and including the model name could leak information into commit history (which may be public). If you plan to use this on repositories with sensitive data, ensure hooks or checks prevent accidental inclusion of secrets and consider reviewing commits manually or disabling autonomous invocation if you want to prevent automatic commits.

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message.

Conventional Commit Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Purpose
feat	New feature
fix	Bug fix
docs	Documentation only
style	Formatting/style (no logic)
refactor	Code refactor (no feature/fix)
perf	Performance improvement
test	Add/update tests
build	Build system/dependencies
ci	CI/config changes
chore	Maintenance/misc
revert	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

• Type: What kind of change is this?
• Scope: What area/module is affected?
• Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

Language: Use Chinese (简体中文) for commit messages.

AI-GEN Footer: Add a footer line to indicate AI-generated code percentage:

AI-GEN: <percentage>%/<lines>行 <model-name>

• <percentage>: Percentage of AI-generated code in this commit
• <lines>: Number of lines changed by AI
• <model-name>: The AI model used (e.g., glm-5, Claude Opus 4.6)

Example:

AI-GEN: 100%/3行 glm-5

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer (Chinese, with AI-GEN)
git commit -m "$(cat <<'EOF'
<type>[scope]: <中文描述>

<可选的详细说明>

AI-GEN: <占比>%/<行数>行 <模型名>
EOF
)"

Best Practices

• One logical change per commit
• Present tense: "add" not "added"
• Imperative mood: "fix bug" not "fixes bug"
• Reference issues: Closes #123, Refs #456
• Keep description under 72 characters
• Use Chinese (简体中文) for commit messages
• Include AI-GEN footer to indicate AI-generated code percentage

Git Safety Protocol

• NEVER update git config
• NEVER run destructive commands (--force, hard reset) without explicit request
• NEVER skip hooks (--no-verify) unless user asks
• NEVER force push to main/master
• If commit fails due to hooks, fix and create NEW commit (don't amend)