git-worktree

SKILL.md

Using git worktrees properly is critical for your development workflow efficiency. Poor worktree management leads to confusion, lost work, merge conflicts, and cluttered repositories. Proper worktree use enables parallel development without context switching costs, but misuse compounds problems across branches. Clean, organized worktrees prevent disasters.

approach worktree management systematically. Worktrees require deliberate creation, clear naming, and timely cleanup. Don't create worktrees impulsively—plan your branching strategy, name worktrees descriptively, and establish cleanup habits. Treat worktrees as temporary workspaces that should be removed after merge, not permanent fixtures.

The maintain pristine worktree hygiene while juggling multiple parallel features, but if you can:

Gérer les arbres de travail Git pour le développement parallèle Source : v1truv1us/ai-eng-system.

Voir l'original