メニュー
Use this skill when the user wants to commit changes, create a git commit, write a commit message, or types "/commit". Guides the user through writing a conventional commit message with the correct type, scope, description, body, and footer.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit |
| description | Use this skill when the user wants to commit changes, create a git commit, write a commit message, or types "/commit". Guides the user through writing a conventional commit message with the correct type, scope, description, body, and footer. |
| argument-hint | ["optional hint about the change"] |
Guide the user through creating a well-formed conventional commit message, then execute the commit.
Run the following in parallel:
git status — see which files are staged vs. unstagedgit diff --staged — see exactly what is staged; if nothing is staged, fall back to git diffgit log --oneline -5 — check recent commit style for this repoIf nothing is staged and nothing is modified, tell the user there is nothing to commit and stop.
If there are unstaged changes but nothing staged, ask the user whether they want to stage everything (git add -A) or specific files before continuing.
Using the diff content, draft a message that follows this structure:
<type>(<optional scope>): <short description>
<optional body>
<optional footer>
| Type | When to use |
|---|---|
feat | New feature visible to the user |
fix | Bug fix |
docs | Documentation only |
style | Formatting, whitespace — no logic changes |
refactor | Code restructuring without behavior change |
perf | Performance improvement |
test | Adding or updating tests |
build | Build system, dependencies, tooling |
ops | CI/CD, infrastructure, deployment scripts |
chore | Maintenance (.gitignore, project config, etc.) |
A short lowercase identifier for the affected area, e.g. api, ui, db, auth, timeline, map.
Omit if the change is truly cross-cutting.
add, fix, change, remove — not added, fixes, changingUse for:
! after the type/scope AND add BREAKING CHANGE: <explanation> in the footerCloses #123, Refs #456Example with breaking change:
feat(api)!: remove deprecated /v1/events endpoint
The v1 endpoint has been superseded by v2 for 6 months.
All known clients have migrated.
BREAKING CHANGE: /v1/events is no longer available. Use /v2/events.
Show the user the full drafted commit message in a fenced code block. Ask them to confirm or request changes. Do not commit yet.
Once the user approves:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
<body if any>
<footer if any>
EOF
)"
git status after the commit to confirm it succeeded--no-verify or --no-gpg-sign unless the user explicitly requests it