Commit prepare

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

全球最大的 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 commit-prepare

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

Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit

SKILL.md

4.6 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Commit Preparation Skill

Automatically prepare commit messages following conventional commits standard.

Activation

This skill activates on keywords:

"commit", "prepare commit", "commit this"
"commit message", "write commit"
"stage and commit", "commit changes"
"what should I commit", "ready to commit"

Workflow

When activated, follow these steps:

1. Gather Context

Run these commands to understand what's being committed:

# See all changes
git status

# Staged changes (what will be committed)
git diff --cached --stat
git diff --cached

# Unstaged changes (won't be committed yet)
git diff --stat

2. Analyze Changes

Determine:

Type: feat, fix, docs, refactor, test, chore, perf, ci
Scope: Which component/module is affected (optional)
Breaking: Are there breaking changes?
What: What was changed
Why: Why was it changed (if not obvious)

3. Generate Commit Message

Follow conventional commits format:

<type>(<scope>): <subject>

<body>

<footer>

Type Reference

Type	When to Use	Example
`feat`	New feature	`feat: add user authentication`
`fix`	Bug fix	`fix: resolve null pointer in parser`
`docs`	Documentation only	`docs: update API reference`
`refactor`	Code restructuring	`refactor: extract validation logic`
`test`	Adding/fixing tests	`test: add unit tests for auth`
`perf`	Performance improvement	`perf: optimize database queries`
`chore`	Maintenance, deps	`chore: update dependencies`
`ci`	CI/CD changes	`ci: add caching to workflow`
`style`	Formatting only	`style: fix indentation`

Rules

Subject: Imperative mood ("add" not "added"), no period, max 50 chars
Body: Wrap at 72 chars, explain what and why (not how)
Footer: Breaking changes, issue references

4. Handle Staging

If there are unstaged changes, ask:

"Stage all changes?" (git add .)
"Stage specific files?" (list them)
"Review changes first?" (show diff)

5. Execute Commit

After user confirms the message:

git add <files>
git commit -m "<message>"

Important: Always use HEREDOC for multi-line commits:

git commit -m "$(cat <<'EOF'
feat: add user authentication

Implement OAuth2 flow with Google and GitHub providers.
Includes session management with secure cookies.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
EOF
)"

6. Post-Commit

After successful commit:

Show git log -1 to confirm
Suggest git push if ready
Mention if more changes remain unstaged

Example Interactions

Simple Commit

User: "commit these changes"

Claude:

git status
git diff --cached

Looking at your staged changes:

Modified src/auth/oauth.py - added token refresh logic
Modified tests/test_auth.py - added refresh tests

Suggested commit:

feat(auth): add OAuth token refresh

Implement automatic token refresh when access token expires.
Includes retry logic with exponential backoff.

Shall I commit with this message?

Breaking Change

User: "ready to commit"

Claude: I see you've changed the API response format. This is a breaking change.

Suggested commit:

feat(api)!: change response envelope format

BREAKING CHANGE: API responses now use { data, meta, errors }
envelope instead of flat response. Clients must update parsing.

Migration: Update response handlers to access .data property.

This marks it as a breaking change with !. Proceed?

Multiple Logical Changes

User: "commit this"

Claude: I see changes to multiple unrelated areas:

Bug fix in parser.py
New feature in export.py
Updated docs

Recommend splitting into separate commits:

fix(parser): handle empty input gracefully
feat(export): add CSV export option
docs: update export documentation

Want me to help stage and commit each separately?

Attribution

Always include Claude attribution for AI-assisted commits:

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Safety Rules

Never use git commit --amend on pushed commits
Never skip hooks with --no-verify unless explicitly asked
Always show the commit message before executing
Check for secrets/credentials in staged files
Warn about large binary files