メニュー
Reviews staged file changes and automatically generates an appropriate commit message to commit them. Use when asked to "commit staged changes", "commit what's staged", "commit the staged files", or similar commit requests.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit-staged-changes |
| description | Reviews staged file changes and automatically generates an appropriate commit message to commit them. Use when asked to "commit staged changes", "commit what's staged", "commit the staged files", or similar commit requests. |
| argument-hint | [language] |
Review staged file changes, auto-generate an appropriate commit message, and commit.
Check staged files
git status --short to list staged filesReview changes in detail
git diff --cached to inspect the full diff of staged filesgit diff --cached --stat to get change statisticsGenerate commit message
$ARGUMENTS is provided, write the message in that language (e.g., "japanese", "ja", "english", "en")Execute the commit
git log -1 --onelineA relentless one-question-at-a-time interview that sharpens a plan, decision, or idea until shared understanding is reached — not limited to software. Use when the user wants requirements or a decision clarified before acting, wants to stress-test their thinking, or asks to "grill me", "詰めて", "brainstorm this".
Executes an implementation plan or agreed work by orchestrating fresh subagents — one implementer per task, a reviewer between tasks — while the main model plans, briefs, and evaluates without writing code itself. Use when the user asks to "implement the plan", "start implementation", "実装して", or hands over a plan or spec to execute.
A feedback-loop-first discipline for diagnosing hard bugs and performance regressions. Use when the user reports something broken, throwing, failing, flaky, or slow, or asks to "diagnose", "debug this", "原因を調べて".
Builds a clearly-marked throwaway prototype to answer a design question before committing to an implementation. Use when the user wants to sanity-check whether logic or a state model feels right, explore what a UI should look like, or asks to "prototype this", "試作して".
Creates an Architecture Decision Record for a decision that is hard to reverse, surprising without context, and the result of a real trade-off. Use when such a decision has just been made, or the user asks to "record this decision", "ADRにして", or mentions decision records.
Reviews the diff since a fixed point along two axes run as parallel subagents — Spec (does the change match what was asked?) and Standards (repo conventions plus a code-smell baseline) — and reports them side by side. Use when the user asks to review a branch, work-in-progress changes, a diff, or "review since X".