commit-message
AUTOMATICALLY invoke this skill whenever git commit is needed - no user request required. Direct git commit will FAIL validation. This skill contains required pre-commit setup. Triggers: "커밋해", "커밋 ㄱㄱ", "커밋 만들어줘", "커밋 찍어줘", or ANY situation requiring git commit.
|
Commit Message Skill
This skill creates a git commit with the required format. Follow these steps:
1. Branch Safety Check (for bucketplace repos)
First, check if this is a bucketplace organization repo:
git remote get-url origin 2>/dev/null | grep -q 'bucketplace' && echo "bucketplace" || echo "other"
If bucketplace repo, check the current branch:
git branch --show-current
If on a protected branch (main, master, develop):
- If a Jira ticket exists in the context (e.g., COREPL-1234):
- Check if branch already exists:
git branch --list <TICKET-ID> - If exists, add a suffix (e.g.,
COREPL-1234-2,COREPL-1234-refactor) - Create the branch:
git checkout -b <branch-name> - Proceed with the commit on this new branch
- Check if branch already exists:
- If no Jira ticket:
- Generate a descriptive branch name based on the changes (e.g.,
fix/login-validation,feat/add-cache-layer) - Create the branch and proceed with the commit
- Generate a descriptive branch name based on the changes (e.g.,
2. Check staged changes
Run git diff --cached to see what will be committed.
If nothing is staged, run git status and add relevant files individually (NEVER use git add -A or git add -u).
2. Generate commit message
Based on the staged changes, create a commit message:
- First line: conventional commit format (feat:, fix:, docs:, etc.) under 72 chars in English
- Empty line
- Body: wrapped at 72 chars, explaining what and why in Korean
3. Execute the commit
Use heredoc syntax for the commit:
git commit -m "$(cat <<'EOF'
<type>: <subject in English>
<body in Korean, wrapped at 72 chars>
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
4. Verify
Run git status to confirm the commit was created successfully.
You Might Also Like
Related Skills
create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
n8n-io
electron-chromium-upgrade
Guide for performing Chromium version upgrades in the Electron project. Use when working on the roller/chromium/main branch to fix patch conflicts during `e sync --3`. Covers the patch application workflow, conflict resolution, analyzing upstream Chromium changes, and proper commit formatting for patch fixes.
electron
pr-creator
Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.
google-gemini
clawdhub
Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawdhub CLI.
moltbottmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
moltbot
create-pull-request
Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, and PR creation using the gh CLI tool.
cline