worktree
/worktree
Create a git worktree for the current repo (named repo-<slug>, placed at <repo-parent>/repo-<slug>), enter an existing worktree, list them, or remove one. Worktrees let the agent or user work on a separate branch in parallel without touching the current checkout.
When to use
- User wants to start parallel work on a branch without losing in-progress state on the current checkout.
- User says "/worktree", "make a worktree for X", "branch off into a worktree", "spin up a sandbox".
- User wants to switch into ("hop into", "enter") an existing worktree to continue prior work.
Do NOT use for plain branch switching (git switch -c) when there is no in-progress work to preserve — a worktree is heavier than a branch.
Subcommands
If the user did not name one, infer:
- create → mentions "new", "make", "spin up", or names a branch/slug that does not match an existing worktree.
- enter → mentions "hop", "enter", "go to", or names a slug/path that matches an existing worktree.
- list → mentions "list", "show", "what worktrees".
- remove → mentions "remove", "delete", "tear down".
More from patrickruddiman/skills
spec
Write a detailed, objective specification of WHAT a system does and WHY. No code, no file paths, no library picks, no implementation prescriptions of any kind. The spec is read by an AI coding agent that will produce its own plan; the spec exists to bound the problem completely — every user-visible behavior, persona task, lifecycle transition, and failure mode.
10slice
Produce a scoped design doc for one technical vertical of a parent spec. Researches the existing codebase first, surfaces implementation choices as questions one at a time, and only drafts the doc after the user resolves them. No code, no tasks — design only.
9create-tasks
Break a slice into AI-executable task files. Each task has a checkbox Tasks section (file paths, line numbers, technical detail — no code) and a strictly code-verifiable Acceptance criteria section that always includes a test command. The consuming AI must tick checkboxes as it works; create-tasks uses that to decide whether to edit a task in place on re-run or append a new one.
9hunt
Aggressively debug, diagnose, or root-cause an issue. Drives a disciplined hunt — query telemetry, reproduce, bisect, instrument, hypothesize-test-confirm, and verify causation by reverting the fix. Refuses common anti-patterns (fix-without-repro, symptom suppression, multi-variable changes, theorize-without-running). Use when the user types /hunt or asks to debug, diagnose, root-cause, track down, or figure out a bug, crash, regression, flaky test, or unexplained behavior.
7schedule
Schedule a one-shot task (Windows/Linux/macOS) to run a command or prompt at a specific time or after a delay. Use when the user says "schedule", "/schedule", "in N minutes/seconds run", "at HH:MM run", "remind me to run", "queue this for later", or wants a task to fire reliably while they step away.
6best-practice
Align a repo or branch with current coding best practices — detect divergences from project conventions and the industry baseline (tests, types, error handling at boundaries, naming, security, observability, documentation), then apply alignment changes one type per commit with tests staying green throughout. Produces commits, not reports. Use when the user says "/best-practice", "align this branch", "best practices pass", "bring this repo up to standard", "fix conventions across this branch", "what's missing from best practices".
4