AgentSkillsCN

commit-message

当用户询问“建议提交信息”“生成提交信息”“我该提交什么”“总结我的改动”“描述我的改动”“提交信息”或输入“/commit-message”时，应使用此技能。它会分析本地Git改动，生成符合规范的提交信息，而无需实际提交。

SKILL.md
--- frontmatter
name: commit-message
description: This skill should be used when the user asks to "suggest a commit message", "generate commit message", "what should I commit", "summarize my changes", "describe my changes", "commit message", or types "/commit-message". Analyzes local git changes and generates a conventional commit message without committing.
disable-model-invocation: true

Commit Message Suggester

Generate a conventional commit message by analyzing all local git changes (staged, unstaged, and untracked) without performing any commit.

Workflow

1. Gather Change Context

Run the following git commands to understand all local changes:

bash
# Staged changes
git diff --cached --stat
git diff --cached

# Unstaged changes to tracked files
git diff --stat
git diff

# Untracked files
git status --short

2. Analyze Changes

Review the gathered information to understand:

  • •What changed: Files added, modified, or deleted
  • •Why it changed: Infer purpose from code context (new feature, bug fix, refactor, etc.)
  • •Scope: Identify the affected component or area of the codebase

3. Generate Conventional Commit Message

Always produce a message following the Conventional Commits specification, regardless of the commit style used in the repository:

code
<type>(<optional scope>): <description>

<optional body>

Types:

  • •feat — New feature or capability
  • •fix — Bug fix
  • •refactor — Code restructuring without behavior change
  • •docs — Documentation only
  • •style — Formatting, whitespace, semicolons (no logic change)
  • •test — Adding or updating tests
  • •chore — Build, CI, dependencies, tooling
  • •perf — Performance improvement

Rules:

  • •Keep the subject line under 72 characters
  • •Use imperative mood ("Add feature" not "Added feature")
  • •Add a body only when the subject line alone is insufficient to explain the change
  • •If changes span multiple concerns, suggest separate commits with guidance on how to stage them

4. Present the Message

Output the suggested commit message in a copyable code block. Do NOT run git commit. If the changes naturally split into multiple commits, present each message separately with instructions on which files to stage for each.

Important

  • •Never commit, stage, or modify any files
  • •This skill is read-only — it only analyzes and suggests
  • •When changes are too broad for a single commit, recommend splitting