메뉴
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | flow-next-opencode-worktree-kit |
| description | Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees. |
Use the manager script for all worktree actions.
ROOT="$(git rev-parse --show-toplevel)"
PLUGIN_ROOT="$ROOT/.opencode/skill"
bash "$PLUGIN_ROOT/flow-next-opencode-worktree-kit/scripts/worktree.sh" <command> [args]
Commands:
create <name> [base]listswitch <name> (prints path)cleanupcopy-env <name>Safety notes:
create does not change the current branchcleanup does not force-remove worktrees and does not delete branchescleanup deletes the worktree directory (including ignored files); removal fails if the worktree is not clean.env* is copied with no overwrite (symlinks skipped).worktrees/ or any worktree path component is a symlinkcopy-env only targets registered worktreesorigin fetch is optional; local base refs are allowedorigin only when base looks like a branch.worktrees/Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.
John Carmack-level implementation review via RepoPrompt or OpenCode. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
Carmack-level plan review via RepoPrompt or OpenCode. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
Local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.
Interview user in-depth about an epic, task, or spec file to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, or clarify a feature before building. Triggers on /flow-next:interview with Flow IDs (fn-1, fn-1.2) or file paths.