メニュー
Create isolated git worktrees with verified clean baselines. Use when the user says "worktree", "isolated branch", "work on multiple branches", or needs feature isolation without switching branches.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate protocol-compliant adapter stubs for Bucket 3 operations requiring external services. Use when the user requests "adapter stub", "dry run", "Bucket 3", "Linear ticket stub", "Kafka stub", or needs a fail-soft fallback for unavailable services.
Refine rough ideas into validated design docs through collaborative dialogue. Use when the user says "brainstorm", "help me design", "explore a feature", "let's think about", or has a vague idea that needs structure before coding.
Add multi-layer validation to fix bugs caused by invalid data. Use when debugging data corruption, invalid input reaching deep execution, "defense in depth", or when a bug needs structural prevention at every layer.
Capture session context for seamless continuity. Use when the user says "handoff", "wrap up", "end session", "pass the baton", "save progress", or needs to preserve working state for the next session.
Adversarial code review that iterates to convergence. Use when the user says "hostile review", "adversarial review", "tear this apart", "find all issues", or needs a thorough skeptical review of code or design.
Convert analysis results or review findings into actionable implementation plans. Use when the user says "turn insights into a plan", "prioritize findings", "action items from review", or has unstructured observations that need to become executable tasks.
| name | using-git-worktrees |
| description | Create isolated git worktrees with verified clean baselines. Use when the user says "worktree", "isolated branch", "work on multiple branches", or needs feature isolation without switching branches. |
Use this skill when starting feature work that needs isolation from the current workspace, or when you need to work on multiple branches simultaneously. The goal is to create an isolated worktree with a verified clean baseline.
Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches without switching. This skill ensures worktrees are created safely with proper directory selection, .gitignore verification, and baseline test confirmation.
Select the worktree directory. Follow this priority order:
.worktrees/ or worktrees/ already exists. If both exist, prefer .worktrees/..worktrees/ (project-local, hidden) or a global location like ~/.config/worktrees/<project>/.Verify .gitignore for project-local directories.
If using a project-local directory (.worktrees/ or worktrees/), check that the directory pattern is in .gitignore. If it is not, add it and commit the change before creating the worktree. This prevents accidentally committing worktree contents.
Create the worktree.
Run git worktree add <path> -b <branch-name>. After creation, install project dependencies by detecting the project type (package.json, pyproject.toml, requirements.txt, Cargo.toml, go.mod) and running the appropriate install command.
Verify a clean baseline. Run the project's test suite in the new worktree. If tests pass, the worktree is ready. If tests fail, report the failures and ask whether to proceed or investigate — do not silently continue with a broken baseline.
Report the worktree location. Output the full path to the worktree, test results summary, and confirmation that the workspace is ready.
A status report containing: