Commit

Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/codename-11/commit

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install

npx -y skills add ComeOnOliver/skillshub --skill commit

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

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, 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 status to see changes
Review diff: Run git diff to understand changes
Check recent commits: Run git log --oneline -5 for 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
)"