MUST use this skill when user asks to commit, create commit, save work, or mentions "커밋". This skill OVERRIDES default git commit behavior. Creates commits following Conventional Commits format with emoji + type/scope/subject (✨ feat, 🐛 fix, ♻️ refactor, etc).
/plugin marketplace add Bae-ChangHyun/cc-plugins-bch/plugin install gitwf@cc-plugins-bchThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Creates commits using the Conventional Commits format with type, scope, and subject components.
# 1. Check project conventions
cat CLAUDE.md 2>/dev/null | head -30
# 2. Review staged changes
git diff --staged --stat
git diff --staged
# 3. Stage files if needed
git add <files>
# 4. Create commit with emoji
git commit -m "✨ feat(scope): add new feature"
Format: emoji type(scope): subject
| Component | Description | Example |
|---|---|---|
| emoji | Visual indicator | ✨, 🐛, ♻️ |
| type | Change category | feat, fix, refactor |
| scope | Affected area (kebab-case) | auth, api-client |
| subject | What changed (imperative mood) | add login validation |
Rules:
| Emoji | Type | Purpose |
|---|---|---|
| ✨ | feat | New feature |
| 🐛 | fix | Bug fix |
| 📝 | docs | Documentation |
| 💄 | style | Formatting/style (no logic change) |
| ♻️ | refactor | Code refactoring |
| ⚡️ | perf | Performance improvement |
| ✅ | test | Add/update tests |
| 🔧 | chore | Tooling, config |
| 🚀 | ci | CI/CD improvements |
| ⏪️ | revert | Revert changes |
Features (feat):
| Emoji | Usage |
|---|---|
| 🧵 | Multithreading/concurrency |
| 🔍️ | SEO improvements |
| 🏷️ | Add/update types |
| 💬 | Text and literals |
| 🌐 | Internationalization/localization |
| 👔 | Business logic |
| 📱 | Responsive design |
| 🚸 | UX/usability improvements |
| 📈 | Analytics/tracking |
| 🚩 | Feature flags |
| 💫 | Animations/transitions |
| ♿️ | Accessibility |
| 🦺 | Validation |
| 🔊 | Add/update logs |
| 🥚 | Easter eggs |
| 💥 | Breaking changes |
| ✈️ | Offline support |
Fixes (fix):
| Emoji | Usage |
|---|---|
| 🚨 | Compiler/linter warnings |
| 🔒️ | Security issues |
| 🩹 | Simple fix for non-critical issue |
| 🥅 | Catch errors |
| 👽️ | External API changes |
| 🔥 | Remove code/files |
| 🚑️ | Critical hotfix |
| ✏️ | Typos |
| 💚 | CI build |
| 🔇 | Remove logs |
Refactor:
| Emoji | Usage |
|---|---|
| 🚚 | Move/rename resources |
| 🏗️ | Architectural changes |
| 🎨 | Improve structure/format |
| ⚰️ | Remove dead code |
Chore:
| Emoji | Usage |
|---|---|
| 👥 | Add/update contributors |
| 🔀 | Merge branches |
| 📦️ | Compiled files/packages |
| ➕ | Add dependency |
| ➖ | Remove dependency |
| 🌱 | Seed files |
| 🧑💻 | Developer experience |
| 🙈 | .gitignore |
| 📌 | Pin dependencies |
| 👷 | CI build system |
| 📄 | License |
| 🎉 | Begin project |
| 🔖 | Release/version tags |
| 🚧 | Work in progress |
Database/Assets:
| Emoji | Usage |
|---|---|
| 🗃️ | Database changes |
| 🍱 | Assets |
Test:
| Emoji | Usage |
|---|---|
| 🧪 | Add failing test |
| 🤡 | Mock things |
| 📸 | Snapshots |
| ⚗️ | Experiments |
MUST FOLLOW: Do not commit per file. Commit per feature unit.
main.py, utils.py, config.yaml to develop Feature A, these 3 files MUST be in a single commit.❌ Bad Example (파일별로 분리 커밋 - 기능 단위가 아님)
git add search.py
git commit -m "✨ feat: create search module"
git add api.py
git commit -m "🐛 fix: fix api connection"
✅ Good Example
git add search.py api.py
git commit -m "✨ feat(search): implement keyword search with API endpoint"
MUST FOLLOW: Do not write conversation history (process). Write only the final code changes (result).
Even if there were 10 modifications during development (error fixes, typo fixes, etc.), the commit message should only state the finally implemented feature.
| ❌ Bad (Process) | ✅ Good (Result) |
|---|---|
| "Fixed typo, fixed A function error, added library to implement login" | ✨ feat(auth): implement JWT-based login |
| "fix api connection and variable name errors and import errors" | ✨ feat(search): implement keyword search |
cat CLAUDE.md 2>/dev/null | head -30
Always check for project-specific commit rules.
git diff --staged --stat
git diff --staged
Understand what's being committed.
Identify:
git commit -m "emoji type(scope): subject"
# Example: git commit -m "✨ feat(auth): add login validation"
For complex changes:
git commit -m "$(cat <<'EOF'
✨ feat(scope): subject
Body explaining WHY and HOW.
Wrap at 72 characters.
Refs: #123
EOF
)"
Add exclamation mark (!) after type/scope for breaking changes:
git commit -m "💥 feat(api)!: change response format"
Or use footer:
git commit -m "$(cat <<'EOF'
💥 feat(api): change response format
BREAKING CHANGE: Response now returns array instead of object.
EOF
)"
When addressing PR review comments:
git commit -m "$(cat <<'EOF'
🐛 fix(scope): address review comment #ID
Brief explanation of what was wrong and how it's fixed.
Addresses review comment #123456789.
EOF
)"
When analyzing diffs, consider splitting commits based on:
| Criteria | Description |
|---|---|
| Different concerns | Changes to unrelated parts of codebase |
| Change types | Feature vs bug fix vs refactoring |
| File patterns | Source code vs documentation vs config |
| Logical grouping | Changes easier to review separately |
| Size | Very large changes that benefit from granularity |
Split Example:
1st: ✨ feat: add new solc version type definitions
2nd: 📝 docs: update documentation for new solc version
3rd: 🔧 chore: update package.json dependencies
4th: 🏷️ feat: add type definitions for new API endpoints
5th: 🧵 feat: improve worker thread concurrency handling
6th: 🚨 fix: resolve linting issues in new code
7th: ✅ test: add unit tests for new solc version features
8th: 🔒️ fix: update dependencies for security vulnerabilities
Before creating a commit, ask yourself:
git added?)git diff content, not conversation log?)✨ feat: add user authentication system
🐛 fix: resolve memory leak in rendering process
📝 docs: update API documentation with new endpoints
♻️ refactor: simplify error handling logic in parser
🚨 fix: resolve linter warnings in component files
🧑💻 chore: improve developer tools setup process
👔 feat: implement business logic for transaction validation
🩹 fix: resolve minor style inconsistency in header
🚑️ fix: patch critical security vulnerability in auth flow
🎨 style: restructure component for better readability
🔥 fix: remove deprecated legacy code
🦺 feat: add input validation for user registration form
💚 fix: resolve CI pipeline test failures
📈 feat: implement tracking for user engagement analytics
🔒️ fix: strengthen authentication password requirements
♿️ feat: improve form accessibility for screen readers
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.