worktree-setup-hook_skill

Overview

This skill provides a post-checkout git hook that automatically configures newly created git worktrees. It detects worktree creation and runs a series of setup tasks so new worktrees are ready to use without manual steps. The hook is a POSIX shell script you can install into .git/hooks/post-checkout and customize to fit your project.

How this skill works

The hook checks whether the previous HEAD is the null ref (0000000000000000000000000000000000000000) to detect new worktrees. When a new worktree is detected it copies environment files, detects the project package manager to install dependencies, and runs optional setup scripts if present and executable. All steps are configurable by editing the hook script.

When to use it

• When adding new git worktrees and you want automatic environment setup
• When you maintain teammates who need consistent worktree bootstrapping
• When you want to copy env files (.env, .env.local) into new worktrees automatically
• When you need dependencies installed automatically for language-specific projects
• When you want to run project-specific setup scripts on worktree creation

Best practices

• Install the hook into .git/hooks/post-checkout and make it executable (chmod +x).
• Keep the hook POSIX-compatible and small; delegate heavy tasks to project scripts (e.g., scripts/setup.sh).
• Provide example env files (like .env.example) and fallback behavior if none exist.
• Detect package managers conservatively and avoid destructive commands; prefer install-only operations.
• Add logging or a dry-run flag to troubleshoot installation steps without side effects.

Example use cases

• Automatically copy .env.example to .env when a new worktree is created so local configuration is immediate.
• Detect package.json and run npm/yarn install in the new worktree to prepare JS projects for development.
• Run scripts/setup.sh to initialize language tools, linters, or code generators right after git worktree add.
• For polyglot repos, detect requirements.txt, go.mod, Cargo.toml, or Gemfile and run the appropriate installer for each language.
• Provide consistent on‑boarding for contributors who use worktrees to review feature branches.