code-branch

To isolate coding work without disturbing your current branch, this skill creates a dedicated git branch using predefined prefixes like feat/, fix/, or exp/ before you start non-trivial development. It enforces naming conventions and communicates the new context to downstream skills.

Use a git worktree instead of a standard branch for long-running tasks or large refactors where you need an isolated physical directory. A standard branch is sufficient for smaller edits, but worktrees provide deeper isolation without disrupting your current working directory.

Branch naming conventions enforced for feature development and experiments require specific prefixes: feat/ for features, fix/ for refactors, and exp/ for experiments. These rules are loaded from shared git-conventions to maintain consistent version-control organization.

Yes, you can use this workflow for large checklist implementations and refactors. It safely isolates these non-trivial coding tasks by setting up a dedicated branch or worktree first, ensuring your main version-control line remains undisturbed until the work is ready.