Describe the feature or problem you'd like to solve
Creating and moving to worktrees with branches that preserve the repo guidelines.
Proposed solution
Today the agent cannot create a worktree and move to it on its own. While the experimental /worktree command exists, it does not allow users to specify the branch name, only the worktree name (the path). Therefore, we can't follow specific repo guidelines such as the creation of hierarchical branches that has / in it, e.g., <USER>/<BRANCH_NAME>.
While allowing agents to create and move to worktrees on its own would in part solve this. This feature request is specific to /worktree slash command. The proposed solution would be to be able to specify the branch name precisely, even when it has / in it.
Example prompts or workflows
No response
Additional context
No response
Describe the feature or problem you'd like to solve
Creating and moving to worktrees with branches that preserve the repo guidelines.
Proposed solution
Today the agent cannot create a worktree and move to it on its own. While the experimental
/worktreecommand exists, it does not allow users to specify the branch name, only the worktree name (the path). Therefore, we can't follow specific repo guidelines such as the creation of hierarchical branches that has/in it, e.g.,<USER>/<BRANCH_NAME>.While allowing agents to create and move to worktrees on its own would in part solve this. This feature request is specific to
/worktreeslash command. The proposed solution would be to be able to specify the branch name precisely, even when it has/in it.Example prompts or workflows
No response
Additional context
No response