Menu
Create a git worktree for parallel development. Use when the user wants to work on a feature branch in a separate directory without switching branches.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Query Discord channel logs from cb-auto-buy service. Use this skill when debugging production issues, checking recent errors, finding purchase history, or investigating service behavior. Retrieves logs without needing SSH access.
Scan log files in ~/Library/Logs for PII leaks (emails, phone numbers, account numbers, names, addresses, SSNs, etc.). Use when verifying PII protection, auditing security, or checking for data leaks in application logs.
Post-session retrospective that analyzes what went well and what needs improvement. Produces actionable findings and optionally updates skills, MEMORY.md, or CLAUDE.md based on lessons learned.
Staff Engineer v2 — same engineering rigor as /staff-engineer but with 3-7x fewer tokens. Uses complexity-based routing, context packages, and inline diffs to eliminate redundant file reads across subagents.
Staff Engineer Swarm — same workflow as /se but uses agent teams (TeamCreate, SendMessage, TaskList) for persistent teammates, parallel research, and structured coordination. Best for MEDIUM/FULL complexity tasks.
Full-lifecycle engineering workflow with deep research, evaluator-optimizer planning, blast-radius analysis, conditional validation, and tiered iteration. Use for significant features, architectural changes, or any task that needs "the full engineering treatment."
| name | worktree |
| description | Create a git worktree for parallel development. Use when the user wants to work on a feature branch in a separate directory without switching branches. |
| disable-model-invocation | true |
| allowed-tools | Bash, Read |
Create a git worktree for working on a separate branch in parallel.
basename $(git rev-parse --show-toplevel)git branch --show-currentgit worktree listParse $ARGUMENTS to determine:
main)Determine the worktree path: Use ../<repo-name>-<branch-name> as the directory (sibling to the current repo).
Check if the branch already exists:
git branch --list <branch-name>
git branch -r --list "origin/<branch-name>"
Create the worktree:
git worktree add <path> <branch-name>git worktree add -b <branch-name> <path> <base-branch>Report the result with the full path so the user can navigate to it.
/worktree feature-auth → Creates ../<repo>-feature-auth on new branch feature-auth from main/worktree fix-bug develop → Creates ../<repo>-fix-bug on new branch fix-bug from develop/worktree existing-branch → If branch exists, checks it out in a new worktreeAfter reporting success, remind the user how to clean up when done:
git worktree remove <path>
# or to also delete the branch:
git worktree remove <path> && git branch -d <branch-name>