Stats
Actions
Tags
From ccx
Automate working on itack issues using git worktrees. (1) Creates a git worktree for the issue in $WORKTREE directory (2) Starts a ccx session in the worktree to work on the issue (3) Provides cleanup commands after the work is merged
How this command is triggered — by the user, by Claude, or both
Slash command
/ccx:worktree-itackThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Worktree Itack Automates the workflow for working on itack issues using git worktrees and ccx sessions. ## Usage ## Workflow When invoked with an issue number, perform these steps: ### 1. Get the issue details Extract the issue title to create a descriptive branch name. ### 2. Create the worktree Get the current project name from the basename of the current working directory. Create a branch name from the issue: `<project>-issue-<number>-<slugified-title>` For example, in project "ccx", issue 15 with title "Add user authentication" becomes `ccx-issue-15-add-user-authenticati...
Automates the workflow for working on itack issues using git worktrees and ccx sessions.
/worktree-itack <issue-number>
When invoked with an issue number, perform these steps:
itack show <issue-number>
Extract the issue title to create a descriptive branch name.
Get the current project name from the basename of the current working directory.
Create a branch name from the issue: <project>-issue-<number>-<slugified-title>
For example, in project "ccx", issue 15 with title "Add user authentication" becomes ccx-issue-15-add-user-authentication.
git worktree add "${WORKTREE}/<project>-issue-<number>-<slug>" -b <project>-issue-<number>-<slug>
The $WORKTREE environment variable must be set to the directory where worktrees should be created.
ccx start --cwd "${WORKTREE}/<project>-issue-<number>-<slug>" "Work on itack issue <number>. When you have completed the work, mark the issue as done with 'itack done <number>' and then commit your changes with a descriptive commit message."
After starting the session, tell the user:
ccx attach <session-name>git worktree remove "${WORKTREE}/<project>-issue-<number>-<slug>"
git branch -d <project>-issue-<number>-<slug>
Note: The session will automatically mark the issue as done with itack done when work is complete, so no need to do this manually.
/worktree-itack 15
In a project named "myapp", this will:
$WORKTREE/myapp-issue-15-<title-slug>npx claudepluginhub camerondavison/ccx --plugin ccx/start-wt-devCreates a git worktree for a GitHub issue, generates a prompt file with issue details, and outputs paths for starting a new Claude Code session.
/create-worktreeCreates isolated git worktree for GitHub issue or PR number. Switches to existing if present, checks out feature branch from default, optionally copies .env files.
/start-issueCreates git worktree for GitHub issue URL with conventional branch name (e.g., feature/123-slug) from labels or title, switches to it, runs init.sh, and adds 'progress' label.
/SKILLResolves GitHub issue via isolated worktree, TDD workflow, and auto-closing PR creation.
/linear-worktreeSets up a git worktree for a Linear issue: fetches details, creates branch off main in parallel directory, copies .env and config/master.key, runs bin/setup, and switches to it.
/feature-flow-wOrchestrates git worktree workflow for features: creates isolated worktree/branch from staged changes or issue number, lints/tests/commits, creates MR. Supports --skip flags and modes.