Git commit

Skill bg-szy/TOP-SKILLS/skills/marketplace/git-commit

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill git-commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow.

SKILL.md

2.6 KB, 619 tokens by cl100k_base, as published. Nobody here has run it

Git Commit

Create well-structured git commits with conventional commit messages based on staged changes.

Parameters

{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "description": "Optional commit message override"
    },
    "type": {
      "type": "string",
      "enum": ["feat", "fix", "docs", "style", "refactor", "test", "chore"],
      "description": "Conventional commit type",
      "default": "auto"
    },
    "scope": {
      "type": "string",
      "description": "Optional scope for the commit"
    }
  }
}

When to Use

User asks to "commit" changes
User wants to "save" their work to git
User asks for help with commit messages
User wants to stage and commit files

Methodology

Phase 1: Status Check

Run git status to see current state
Run git diff --staged to see staged changes
Run git diff to see unstaged changes
Check recent commit history for message style

Phase 2: Analysis

Categorize Changes: Identify what changed (new files, modifications, deletions)
Determine Type: Is this a feature, fix, refactor, etc.?
Identify Scope: What component/module is affected?
Summarize Purpose: What does this change accomplish?

Phase 3: Commit Creation

Stage relevant files if not already staged
Generate conventional commit message
Execute the commit
Verify success with git status

Phase 4: Output

Report:

What was committed
The commit message used
The new commit hash

Guidelines

Follow Conventional Commits format: type(scope): description
Keep subject line under 72 characters
Use imperative mood ("Add feature" not "Added feature")
Don't commit sensitive files (.env, credentials, etc.)
Don't use --force or --amend unless explicitly requested
Include meaningful description of WHY, not just WHAT

Examples

Example 1: Auto Commit

User Input: "Commit my changes"

Expected Behavior:

Run git status and git diff to understand changes
Analyze the nature of changes
Generate appropriate commit message
Stage files if needed
Create commit and report success

Example 2: Specific Type

User Input: "创建一个 fix 类型的 commit"