メニュー
Create, remove, or prune git worktrees for issue/PR isolation. Use when the user asks for a worktree, wants an isolated workspace per issue, or wants completed worktrees cleaned up.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Address pull request review feedback from humans or bots. Use when existing comments, requested changes, unresolved review threads, or CodeRabbit/codex review findings need code fixes, verification, push updates, and thread resolution. SKIP fresh code-review requests with no existing feedback; use review-deep.
Take a GitHub issue from implementation to merged PR. Use for 'complete issue #N', 'finish this issue end-to-end', or fully autonomous issue-to-merge requests. SKIP issue startup without merge intent; use start-issue.
Run end-to-end PR verification with browser testing. Use before merge or in fix-and-ship mode when the user asks to verify a PR, run E2E, browser-test, or visually check UI changes. SKIP backend-only checks with no browser/UI path; use review-deep or ship as appropriate.
Start implementation of a GitHub issue: fetch context, prepare worktree flow, implement with TDD, verify, and submit PR. Use for 'start issue #N', issue URLs, or requests to begin issue work. SKIP fully autonomous issue-to-merge requests; use complete-issue.
Start issue work in a new tmux window with its own worktree. Use when the user has tmux running and wants issue startup to continue outside the current session. SKIP when not inside a tmux session ($TMUX unset) or when the user wants to work in the current session; use start-issue directly.
Ship a PR end-to-end: verify locally, push, create/update the PR, watch CI, handle review feedback, and merge without admin override. Use for 'ship', 'ship it', or 'push and merge'. SKIP if the user only wants a PR opened; use `create-pr`.
| name | worktree |
| description | Create, remove, or prune git worktrees for issue/PR isolation. Use when the user asks for a worktree, wants an isolated workspace per issue, or wants completed worktrees cleaned up. |
| disable-model-invocation | true |
Manage git worktrees for isolated per-issue/per-PR work. Three sub-actions, each in its own sibling file.
| User intent | Sibling | Slash command |
|---|---|---|
| Create one worktree for an issue or PR | create.md | /create-worktree <num> |
| Remove a specific worktree (interactively) | remove.md | /remove-worktree |
| Batch-clean all completed worktrees | prune.md | /prune-worktree |
Match the user's request to one of the three rows, then read the corresponding sibling for the full procedure.
../<reponame>-issue-<num>-<title-slug>/ — sibling to the source repo, never inside itissue-<num>-<title-slug>gh issue view --json titleissue-<NUM>- prefix is the trusted issue marker on a branch — fix/2fa-login contains a number but is NOT an issue branchgit remote show origin | grep 'HEAD branch' (handles repos with main vs master vs custom)${CLAUDE_PLUGIN_ROOT}/scripts/worktree-state.sh registers the active worktree so the pre-tool-use hook blocks accidental edits to the source repogh CLI installed and authenticatedcreate.md — full create procedure (PR vs issue detection, env-file copy, state registration)remove.md — interactive selection + safety-check matrix (issue closed? branch merged? uncommitted changes?)prune.md — batch evaluation, classification, confirmation, removal