What problem does it solve?
It prevents feature-branch work from polluting your current workspace by ensuring a clean starting state and using Git worktree to isolate changes while sharing the same environment.
Core Features & Use Cases
- Workspace safety checks: Refuses to create a new feature branch when
git status --short indicates uncommitted changes, and reports what needs commit or stash.
- Consistent branch naming: Accepts a provided branch name or infers one from context, then normalizes it to a
feature/ or hotfix/-style pattern.
- Isolated work via git worktree: Creates and enters a dedicated worktree for the branch, then validates shared developer links like
.venv and .claude/.
- Example use case: Starting a refactor for the dice rules should happen in its own isolated worktree so builds, logs, and experiments don’t interfere with ongoing development.
Quick Start
Ask to create a feature branch named "feature/roll-refactor" from the latest master, using git worktree isolation and validating .venv and .claude links before switching to the worktree.