メニュー
Generate a conventional commit message from staged changes or a diff. Follows Conventional Commits spec (feat/fix/chore/refactor/docs/test/perf/ci).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
View and manage Google Calendar events
Check and manage Gmail inbox
Create and manage notes in Notion
Search the web for information using Exa
Review code for bugs, security issues, performance problems, and style. Accepts a file path, diff, or inline code snippet.
Structured debugging session. Accepts an error message, stack trace, or description of unexpected behaviour. Works through reproduce → isolate → hypothesize → verify → fix.
| name | commitmsg |
| description | Generate a conventional commit message from staged changes or a diff. Follows Conventional Commits spec (feat/fix/chore/refactor/docs/test/perf/ci). |
| argument-hint | [{"optional":"file paths or description"}] |
| allowed-tools | Bash |
$ARGUMENTS
git diff --staged to see staged changes (or git diff HEAD if nothing staged)$ARGUMENTS mentions specific files, focus on those<type>(<scope>): <short summary>
<optional body: what changed and why, wrapped at 72 chars>
<optional footer: BREAKING CHANGE: ..., Closes #123>
Types: feat (new feature), fix (bug fix), perf (performance), refactor (no behaviour change), docs (documentation only), test (tests only), chore (tooling/deps), ci (CI/CD), style (formatting)
Rules:
feat(auth):, fix(cli):)BREAKING CHANGE: in footerCloses #N or Fixes #NPrint the ready-to-use commit message in a code block so it can be copied directly. If the changes span multiple unrelated concerns, suggest splitting into separate commits.