Git commit skills chemiseblanc git commit

Skill bg-szy/TOP-SKILLS/skills/marketplace/git-commit__skills-chemiseblanc-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__skills-chemiseblanc-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

Guide for breaking changes into logical, atomic commits using interactive staging. Use when committing changes that span multiple concerns, when needing to stage parts of files (hunks), when asked to create well-organized commit history, or when changes should be split into multiple commits.

SKILL.md

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

Git Commit

Break changes into logical, atomic commits using interactive staging.

Workflow

Analyze all changes
Identify logical units (one concern per commit)
Stage relevant changes (whole files or hunks)
Commit with a good message
Repeat until all changes are committed

Analyzing Changes

git status                 # overview of changed files
git diff                   # unstaged changes
git diff --cached          # staged changes
git diff HEAD              # all changes (staged + unstaged)

Look for natural boundaries: different features, bug fixes, refactors, or config changes.

Identifying Logical Commits

Each commit should represent one logical change. Signs that changes belong in separate commits:

Different purposes (bug fix vs feature vs refactor)
Unrelated files or components
Changes that could be reverted independently
Separate items from a PR review or task list

Common groupings:

Related files implementing a single feature
A bug fix with its test
Rename/move operations separate from behavior changes
Config or dependency changes separate from code

Staging Strategies

Whole files

git add <file>             # stage entire file
git add <dir>/             # stage all files in directory
git reset HEAD <file>      # unstage file

Partial files (hunk staging)

Use git add -p to stage specific hunks within a file:

git add -p                 # interactively stage hunks from all files
git add -p <file>          # interactively stage hunks from specific file

Hunk commands:

y - stage this hunk
n - skip this hunk
s - split into smaller hunks (if hunk contains multiple changes)
q - quit, keeping already-staged hunks
? - show help

Verify staged changes

git diff --cached          # review exactly what will be committed

Commit Messages

Use the commit-message skill for formatting. Key points:

Conventional Commits format: type(scope): description
Imperative mood ("Add feature" not "Added feature")
Explain why in the body, not what (the diff shows what)

Repeat

After each commit:

git status                 # check remaining changes
git log --oneline -3       # verify commit was created

Continue staging and committing until all changes are organized into logical commits.