git-commit
GitHub基于已暂存的代码变更生成符合规范的 Git 提交。自动分析差异以推断类型、范围、摘要和风险，并执行 git commit 创建包含详细变更说明和风险评估的提交记录。
Trigger Scenarios
Install
npx skills add NeverSight/learn-skills.dev --skill git-commit -g -y
SKILL.md
Frontmatter
{
"name": "git-commit",
"description": "Generate and create clean git commits from staged changes. Use when the user asks to commit already staged work, generate a commit message from `git diff --cached`, or run a commit workflow that infers type, scope, subject, body, and risk from the staged diff."
}
Git Commit
Generates a clean commit with a properly formatted message from staged changes.
Usage
/git-commit
Required before running: Stage your code files with git add <files>
Step 1: Analyze Staged Changes
Run these commands before composing the commit:
git diff --cached --stat
git diff --cached
If nothing is staged, stop and tell the user to stage files first.
Step 2: Infer Commit Details
Automatically determine from the diff:
-
Change type: Infer from file paths and diff content:
docs/*.md,*.mdchanges →Docscmd/,internal/,pkg/with new functionality →Featurefix,bug,hotfixin messages →BugfixorCritical-Fixrefactor,rename,extract→Refactorperf,optimize,faster→Perf- Default to
Featureif ambiguous
-
Scope: Infer from the most relevant directory, package, module, or feature area. Keep it short and lowercase.
-
Summary: Generate from the most meaningful changed files/functions. Focus on what changed not how.
-
Risk Analysis: Evaluate:
- Scope of changes (small = low risk, wide = higher risk)
- Whether critical paths are affected (auth, payment, data)
- If tests are included
- Breaking API changes
Step 3: Create Commit WITHOUT Co-Authored-By or Signed-off-by
Use plain git commit (without -s or -a flags):
git commit -m "[Type](scope): Subject
Body explaining the changes in detail.
- Specific key point derived from actual diff
- Another specific key point from the changes
- Technical implementation detail from the code
Risk: <risk_analysis from Step 2>"
⚠️ CRITICAL: Replace placeholder bullets with actual content from the diff. Never use literal placeholders like "Key point 1" - extract specific details from what actually changed.
Important: Do NOT use the Co-Authored-By line or Signed-off-by line. The commit should only contain the message body above.
Available Types
⚠️ Use EXACTLY these types (case-sensitive):
| Type | Description |
|---|---|
Feature |
New feature or functionality |
Bugfix |
Bug fix |
Refactor |
Code refactoring without changing behavior |
Critical-Fix |
Critical/security bug fix |
Docs |
Documentation changes |
Perf |
Performance improvements |
Commit Message Format
The generated commit follows this format:
[Type](scope): Subject
Body explaining the changes in detail.
- Specific key point from the diff
- Another specific key point from changes
- Concrete technical detail from code
Risk: <risk_analysis from Step 2>
⚠️ Never use literal placeholders. Always extract real content from the diff.
Version History
- e0220ca Current 2026-07-05 23:29
