メニュー
Cluster changes into logical commits and create Conventional Commits. Invoke with `/commit` or `/commit <message>`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Address the latest review feedback on the current branch's open PR. Fetches comments, triages relevance, implements fixes or replies with reasoning, then commits.
Create a pull request for the current branch. Analyzes all commits, runs validation, and opens a well-formatted PR on GitHub. Always targets `main`. Invoke with `/pr-open`.
Analyze the repo stack, customize wt-setup.sh for worktree-aware development, and run a health check. Use this when the user just installed the worktree tools and needs to configure them, when they changed their stack and need to update the setup script, or when they want to check if their repo is worktree-friendly. Also triggers for `/wt-adopt [--check-only]`.
Batch cleanup of stale worktrees and orphaned branches. Use this when the user wants to tidy up, has accumulated worktrees over time, asks about old branches, or mentions cleaning up their workspace. Also triggers for `/wt-cleanup [--dry-run]`.
Finish work in a worktree — push, remove the worktree, and optionally delete the branch. Use this when the user is done with a worktree, wants to clean up, push and move on, or mentions they no longer need a parallel environment. Also triggers for `/wt-close [branch] [--push] [--force]`.
Answer common questions about working with worktrees — VSCode integration, gitignore, port offsets, env files, workflow tips. Use this when the user asks how worktrees work, why something looks different in their editor, how to see diffs, or has any question about the worktree setup. Also triggers for `/wt-help [topic]`.
| name | commit |
| description | Cluster changes into logical commits and create Conventional Commits. Invoke with `/commit` or `/commit <message>`. |
| allowed-tools | Bash Read Glob Grep |
| argument-hint | [commit message] |
| context | fork |
| agent | commit |
Cluster all pending changes into logical groups and create a separate Conventional Commit for each group. Execute immediately — do NOT propose or ask for confirmation.
If a single argument is provided (e.g., /commit feat: add login page), stage everything and commit with that message as a single commit.
Otherwise, analyze the changes, cluster them by logical purpose, and create one commit per cluster.
IMPORTANT: Do NOT push to the remote — this skill only creates local commits. The human handles pushing.
IMPORTANT: Launch the commit agent and let it run to completion autonomously. Do NOT summarize or preview the clusters before committing — just execute. When the agent returns, relay its summary table to the user.
