Commit skills codename 11 commit
Skill bg-szy/TOP-SKILLS/skills/marketplace/commit__skills-codename-11-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
npx -y skills add bg-szy/TOP-SKILLS --skill commit__skills-codename-11-commitAssembled 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
Create well-formatted git commits with conventional commit messages and emoji. Use when user asks to commit changes, save work, or after completing a task that should be committed.
SKILL.md
2.4 KB, 585 tokens by cl100k_base, as published. Nobody here has run it
Commit Skill
Create well-formatted commits with conventional commit messages and emoji prefixes.
When to Use
- User explicitly asks to commit changes
- User asks to "save" or "commit" their work
- After completing a significant task (ask user first)
- User says "commit this" or similar
Process
- Check status: Run
git statusto see changes - Review diff: Run
git diffto understand changes - Check recent commits: Run
git log --oneline -5for commit style reference - Stage files: If no files staged, add relevant files with
git add - Analyze changes: Determine if multiple commits are needed
- Create commit: Use conventional commit format with emoji
Commit Message Format
<emoji> <type>: <description>
[optional body]
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <[email protected]>
Commit Types with Emoji
| Type | Emoji | When to Use |
|---|---|---|
feat: | ✨ | New feature |
fix: | 🐛 | Bug fix |
docs: | 📝 | Documentation |
refactor: | ♻️ | Code refactoring |
chore: | 🔧 | Build/tooling |
perf: | ⚡️ | Performance |
test: | ✅ | Tests |
style: | 🎨 | Code formatting |
ci: | 🚀 | CI/CD changes |
fix: | 🔒️ | Security fix |
chore: | 🔖 | Release/version tag |
Git Safety Rules
- NEVER update git config
- NEVER use destructive commands (push --force, hard reset) unless explicitly requested
- NEVER skip hooks unless explicitly requested
- NEVER amend commits that have been pushed
- NEVER commit files that may contain secrets (.env, credentials.json)
Splitting Commits
Consider multiple commits when changes involve:
- Different concerns (unrelated code areas)
- Different types (features + fixes + docs)
- Different file patterns (source vs documentation)
Example
git add src/components/NewFeature.tsx src/services/feature.ts
git commit -m "$(cat <<'COMMIT'
✨ feat: add user authentication system
Implements login, logout, and session management.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <[email protected]>
COMMIT
)"