AgentSkillsCN

git-commit

执行 git commit 操作时，支持常规提交信息分析、智能暂存功能，以及自动生成功能。当用户提出提交更改、创建 git commit，或提及“/commit”时，此技能便能派上用场。它具备以下功能：(1) 自动从变更内容中识别提交类型与范围；(2) 根据 diff 自动生成常规提交信息；(3) 支持交互式提交，允许用户灵活覆盖提交类型、范围或描述；(4) 提供智能文件暂存功能，便于按逻辑分组归档。

SKILL.md
--- frontmatter
name: git-commit
description: 'Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping'
license: MIT
allowed-tools: Bash

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

code
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

TypePurpose
featNew feature
fixBug fix
docsDocumentation only
styleFormatting/style (no logic)
refactorCode refactor (no feature/fix)
perfPerformance improvement
testAdd/update tests
buildBuild system/dependencies
ciCI/config changes
choreMaintenance/misc
revertRevert commit

Breaking Changes

code
# 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

bash
# 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 & Group by Context

Review the changes and determine if they belong to a single logical change or multiple distinct changes.

Logical Grouping Strategy:

  • •Split by Context: If changes cover multiple independent contexts (e.g., a refactor, a new feature, and a doc update), create separate commits for each.
  • •Order Matters: Commit prerequisites (e.g., refactors, dependency updates) before the features that use them.
  • •Atomic Commits: Each commit must be self-contained and leave the codebase in a working state.

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

bash
# 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)

4. Execute Commit

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

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<optional body>

<optional footer>
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

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)