AgentSkillsCN

git-commit

执行git commit，结合传统提交消息分析、智能暂存及消息生成。适用于用户要求提交更改、创建git commit或提及“/commit”时。支持：(1) 自动从更改中检测类型与范围，(2) 根据diff生成传统提交消息，(3) 交互式提交，可选覆盖类型/范围/描述，(4) 智能文件暂存以实现逻辑分组。

SKILL.md
--- frontmatter
allowed-tools: Bash
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
metadata:
    github-path: git-commit
    github-pinned: 6d50a7587e0ff372277dc4a33ccb8b8ea2ff7470
    github-ref: 6d50a7587e0ff372277dc4a33ccb8b8ea2ff7470
    github-repo: https://github.com/devantler-tech/skills
    github-tree-sha: 883a6a7466f55a9cd9f22cf1cce2d9333fc9b998
name: git-commit

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 (if needed)

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)