worktree-safety

To keep experimental code off the main branch, you should always create a feature branch first. This workflow ensures isolation by enforcing branch creation and a baseline test before any code changes are made.

A baseline test is required before starting a new feature to verify the branch is safe for coding. It establishes a passing baseline that ensures your new multi-commit tasks or experiments do not introduce regressions to main.

The best way to isolate multi-commit tasks is using a git worktree feature branch. Creating a dedicated branch ensures risky work happens in isolation, protecting the main branch until your changes are fully ready.

To create a safe feature branch for testing, check your current branch, create a new task branch, run baseline tests, and confirm readiness. This process guarantees your code changes remain isolated from main.

You should use a feature branch whenever starting new features, multi-commit tasks, or trying experiments. This approach protects main by enforcing isolation and preventing risky work from happening directly on the baseline.

Yes, this branching workflow applies to prompts to try experiments. It enforces branch creation and a baseline test so that any experimental or risky work is safely isolated from the main branch.