メニュー
Creates clean, atomic commits following Conventional Commits specification. Use when committing code changes, writing commit messages, or when user mentions commit, conventional commits, or atomic commits.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/mazrean/agent-skills --skill committing-codeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | committing-code |
| description | Creates clean, atomic commits following Conventional Commits specification. Use when committing code changes, writing commit messages, or when user mentions commit, conventional commits, or atomic commits. |
Create well-structured, atomic commits that follow Conventional Commits specification.
Use this skill when making commits, writing commit messages, splitting changes into logical units, or following project commit conventions.
Supporting files: CONVENTIONAL-COMMITS.md for commit message format, ATOMIC-COMMITS.md for splitting changes.
# Stage specific changes (not all at once)
git add -p
# Commit with conventional format
git commit -m "feat(parser): add support for array parsing"
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Common types:
| Type | Purpose | SemVer |
|---|---|---|
feat | New feature | MINOR |
fix | Bug fix | PATCH |
docs | Documentation only | - |
style | Formatting, whitespace | - |
refactor | Code restructure, no behavior change | - |
perf | Performance improvement | - |
test | Adding/fixing tests | - |
chore | Build, tooling, deps | - |
ci | CI/CD configuration | - |
When committing, follow these steps:
Commit Workflow:
- [ ] Step 1: Review all changes (git diff)
- [ ] Step 2: Identify logical units of work
- [ ] Step 3: Stage changes for first unit (git add -p)
- [ ] Step 4: Write commit message (conventional format)
- [ ] Step 5: Verify commit is atomic (single purpose)
- [ ] Step 6: Repeat for remaining units
git status
git diff
Look for mixed concerns:
Each commit should be:
Bad (mixed concerns):
Add user authentication and fix typo in README and update deps
Good (separate commits):
feat(auth): add user authentication
docs: fix typo in README
deps: update lodash to 4.17.21
Use interactive staging to pick specific changes:
# Stage by hunks
git add -p
# Commands in interactive mode:
# y - stage this hunk
# n - skip this hunk
# s - split into smaller hunks
# e - manually edit hunk
# q - quit
Format:
<type>(<scope>): <imperative description>
<body explaining why, not what>
<footer with references/breaking changes>
Examples:
Simple fix:
fix(api): handle null response from payment gateway
Feature with body:
feat(search): add fuzzy matching for product names
Users frequently misspell product names. Fuzzy matching
improves search success rate by ~40% based on analytics.
Closes #234
Breaking change:
feat(api)!: change authentication to OAuth2
BREAKING CHANGE: API now requires OAuth2 tokens instead of
API keys. See migration guide in docs/auth-migration.md.
Before finalizing, check:
Continue staging and committing remaining logical units.
# You've made many changes. Split them:
git stash # Save current state
git stash show -p | head # Review what you have
git checkout -p stash # Selectively apply changes
git add -p # Stage first logical unit
git commit -m "refactor: ..."
# Repeat until stash is empty
# Made a mistake in last commit (not yet pushed)
git add <files>
git commit --amend --no-edit
# Or with new message
git commit --amend -m "fix: corrected message"
# Squash/reorder last N commits
git rebase -i HEAD~N
# In editor:
# pick abc1234 feat: add feature
# fixup def5678 fix typo
# squash ghi9012 more changes
Closes #123, Fixes #456feat: add new feature