メニュー
Group git changes by logical concern and generate a commit message for each group — follows Conventional Commits 1.0.0 and commitlint rules
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit |
| description | Group git changes by logical concern and generate a commit message for each group — follows Conventional Commits 1.0.0 and commitlint rules |
| metadata | {"phase":"commit","input":"git diff or description of changes; optionally \"and commit\" to also run the commits","output":"grouped file changes with commit message for each group; commits if asked"} |
Use this skill when the user:
Before running git diff:
git diff if context is missing or unclearAnalyze the changes, group file changes by logical concern, and generate one Conventional Commits 1.0.0 message per group.
Output grouped changes with commit messages only — no fluff.
If the prompt asks to commit, commit each group after user confirmation.
Group file changes by logical concern, e.g.:
onboard-project.md in one group, implement.md in anotherKey principle: one commit per logical, independently shippable concern — not one per file.
Header: <type>(<scope>): <subject> (72 chars max)
Body: (if needed, blank line after header, 100 chars/line)
Footer: (if needed, blank line after body)
BREAKING CHANGE: <description>Closes #123Breaking change: add ! after scope, e.g. feat(api)!: remove old endpoint
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| chore | Routine tasks, no src/test changes |
| docs | Documentation only |
| refactor | Code change that neither fixes a bug nor adds a feature |
| test | Adding or correcting tests |
| style | Formatting, whitespace (no logic change) |
| perf | Performance improvement |
| ci | CI configuration changes |
| build | Build system or dependency changes |
| revert | Reverts a previous commit |
| i18n | Internationalization / localization |
For each group:
## Group 1: <description>
- file1.md
- file2.md
<type>(<scope>): <subject>
[optional body]
[optional footer]
---
## Group 2: <description>
- file3.md
- file4.md
<type>(<scope>): <subject>
Separate groups with ---.
! or BREAKING CHANGE: footerCreate GitHub pull requests — picks the most token-efficient available method (gh CLI, GitHub MCP, or git push), and sources the PR body from an existing spec/plan instead of re-analyzing the diff
Prime — load project context by reading docs, the docs_context layer, core docs, and TODO before starting any task
Feature planning — research codebase, design options, write a structured spec/implementation plan to the project specs directory
Generate feature documentation by analyzing code changes and specifications — creates markdown docs in docs/core/ with conditional context
Bootstrap any project's AI workspace — detect the current tool, extract hardcoded paths from skill/command/agent files, write a central workspace.md, update all files to use config keys
Build or refresh the codebase graph indexes (codebase-memory-mcp structural index + graphify semantic graph) that other skills read from. The single writer — idempotent, incremental, safe to call repeatedly.