Menu
Create or update a git worktree for a branch
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | worktree |
| description | Create or update a git worktree for a branch |
| disable-model-invocation | true |
The user wants to work on a branch in a separate worktree. The argument is provided as: $ARGUMENTS.
If no argument was provided, ask the user which branch or issue they want.
Follow these steps:
Fetch latest from remote by running git fetch origin.
Determine the branch name:
git branch -a), use it as-is.#82 or 82), generate a descriptive branch name in the format <number>-short-descriptive-kebab-case-name. Use context from the issue (fetch it with gh issue view <number>) to pick a short but descriptive name. For example, issue #82 titled "Unify not-found and unauthorized responses" could become 82-unify-not-found-responses.Determine the worktree path: ../careless-<branch-name> (relative to the repo root). For example, branch azure-session-lifetime-management becomes ../careless-azure-session-lifetime-management.
Check if the worktree already exists by running git worktree list and checking if the path is already listed.
Ask the user for confirmation before creating or updating the worktree. Show the branch name and worktree path and ask if they want to proceed.
If the worktree does NOT exist:
git worktree add ../careless-<branch-name> <branch-name> to create it.git worktree add -b <branch-name> ../careless-<branch-name> origin/<branch-name> to create a local branch tracking the remote.git worktree add -b <branch-name> ../careless-<branch-name> origin/master.If the worktree ALREADY exists:
git -C ../careless-<branch-name> pull to get the latest changes.Tell the user how to start working there. Print a message like:
Worktree ready! To start Claude in the worktree, run:
cd ../careless-<branch-name> && claude
Create a git commit with a short, lowercase commit message
Use when the user wants to create a GitHub issue from a rough problem description or feature idea
Create a pull request with a structured description covering why, what, challenges, and future work
Analyze a GitHub issue and develop an implementation plan
Review all changes on the current branch compared to master
Review unstaged git changes for bugs, logic errors, and security problems