ZES-using-git-worktrees

Isolating feature development with git worktrees is automated by this skill to prevent workspace pollution. It detects existing workspaces, creates isolated environments using native git integration, and verifies directory ignore status to ensure your current branch remains untouched during feature implementation.

An isolated git worktree is needed when starting a new feature that requires a clean environment for branch isolation and dependency setup. It prevents context-switching overhead by allowing you to run tests and implement changes in a separate directory while keeping your main workspace clean.

Automating git worktree creation is handled by this skill through native git integration and project-specific directory conventions. It safely provisions environments by verifying baseline test integrity and checking directory ignore status to prevent accidental commits of worktree contents during software engineering workflows.

Baseline test verification is enforced as a safety guardrail during automated worktree creation. The skill ensures baseline test integrity and checks directory ignore status before provisioning the isolated environment, preventing accidental commits and maintaining a safe baseline for feature development.

Automated git worktrees can be used with existing project directory conventions by adhering to the project-specific directory structures required for safe environment provisioning. The skill requires native git integration and applies these conventions to ensure proper workspace isolation and baseline test verification.

Git worktree setup risks accidental commits when directory ignore status is not properly verified. This skill prevents accidental commits of worktree contents by applying safety guardrails that verify ignore status and baseline test integrity during the automated creation of isolated development environments.