메뉴
Use when the user asks about Codex worktrees, isolated task branches, or multi-repo task environments. In this repo, all worktree-style management goes through the local `spaces` CLI and the `codex --spaces` shell shortcut.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write, refactor, debug, and review application code with validated boundaries, canonical domain types, explicit dependency lifetimes, pseudocode-like orchestration, local code over gratuitous helpers, deliberate effects and observability, and minimal critical-path tests. Use for substantive business logic, data modeling, state and error flows, API/CLI/env/queue/persistence/file/third-party boundaries, and design-focused code review.
Write, refactor, debug, and review application code with validated boundaries, canonical domain types, explicit dependency lifetimes, pseudocode-like orchestration, local code over gratuitous helpers, deliberate effects and observability, and minimal critical-path tests. Use for substantive business logic, data modeling, state and error flows, API/CLI/env/queue/persistence/file/third-party boundaries, and design-focused code review.
Use when reading, summarizing, analyzing, comparing, or extracting from Notion pages, databases, URLs, or docs in read-only tasks; prefer materializing the full target into a local temp Markdown, JSON, HTML, or text file before analysis instead of repeatedly reading MCP chunks; do not use for Notion create, update, or write operations.
Use when reading, summarizing, analyzing, comparing, or extracting from Notion pages, databases, URLs, or docs in read-only tasks; prefer materializing the full target into a local temp Markdown, JSON, HTML, or text file before analysis instead of repeatedly reading MCP chunks; do not use for Notion create, update, or write operations.
Use only when explicitly invoked for an expensive multi-agent code review and iterative fix loop. Reviews the current branch, PR, commit range, file list, or requested target for consistency problems, race conditions, missing static type safety, and inconsistent style or naming, then fixes verified issues one at a time with tests, commits, and push.
Use only when explicitly invoked for an expensive multi-agent code review and iterative fix loop. Reviews the current branch, PR, commit range, file list, or requested target for consistency problems, race conditions, missing static type safety, and inconsistent style or naming, then fixes verified issues one at a time with tests, commits, and push.
| name | spaces |
| description | Use when the user asks about Codex worktrees, isolated task branches, or multi-repo task environments. In this repo, all worktree-style management goes through the local `spaces` CLI and the `codex --spaces` shell shortcut. |
| metadata | {"short-description":"Manage Codex worktree-style flows with `spaces`"} |
Use this skill for Codex workspace management in this dotfiles setup.
Trigger this skill for:
spaces workspacesspaces workflow in this repo.spaces for all worktree-style management.codex --spaces when the user wants to create and launch a fresh Codex workspace directly.spaces CLI directly for discovery and cleanup.Supported wrapper patterns:
codex --spaces [repo-path ...]codex --spaces [repo-path ...] --name <workspace-name>codex --name <workspace-name> --spaces [repo-path ...]codex --spaces [repo-path ...] -- --model gpt-5.4Wrapper rules:
--spaces and --name are the only wrapper-owned flags before --.-- is forwarded to the real Codex CLI unchanged.--name sets both the workspace name and branch name.--name if that branch already exists locally or as a remote-tracking branch in any provided repo.The wrapper resolves targets like this:
That means the default behaves like the old single-repo worktree flow when a space contains one repo, but still supports multi-repo task spaces cleanly.
Use the spaces CLI directly when you need discovery or cleanup:
spaces list --json
spaces show <space> --json
spaces create <repo>... --json
spaces remove <space> --yes --keep-branches
spaces remove <space> --yes --delete-branches
Key details:
spaces create requires the source repo to have an origin remote.spaces create based new workspaces on the source repo's upstream default branch rather than the currently checked out feature branch.CODEX_SPACES_BASE_DIR overrides the default base directory for both the wrapper and direct CLI usage when you pass --base-dir consistently.If the task spans multiple repos, create one space containing all of them and root Codex at the space root unless the user explicitly wants one repo only.