docs: add copy .env example and link from README

Author: timvw

README.md

@@ -19,7 +19,7 @@ Inspired by [haacked/dotfiles/tree-me](https://github.com/haacked/dotfiles/blob/
 - **Interactive selection menus** with fuzzy matching for checkout, remove, pr, and mr commands
 - GitHub PR support via `wt pr` command (uses `gh` CLI) — checks out the PR's actual branch name
 - GitLab MR support via `wt mr` command (uses `glab` CLI) — checks out the MR's actual branch name
-- **Pre/post command hooks** — run custom scripts on create/checkout/remove (e.g. [launch AI assistants](docs/examples.md#ai-assistants-and-editors), [share build caches](docs/examples.md#shared-build-cache-across-worktrees), [assign dev server ports](docs/examples.md#deterministic-dev-server-port-per-worktree), copy `.env`)
+- **Pre/post command hooks** — run custom scripts on create/checkout/remove (e.g. [launch AI assistants](docs/examples.md#ai-assistants-and-editors), [share build caches](docs/examples.md#shared-build-cache-across-worktrees), [assign dev server ports](docs/examples.md#deterministic-dev-server-port-per-worktree), [copy `.env`](docs/examples.md#copy-env-to-new-worktrees))
 - **Stale worktree detection** — find worktrees with deleted remote branches or inactive commits (`wt cleanup --stale`)
 - **Color-coded status output** — green (clean), red (dirty), yellow (ahead/behind), bold cyan (current); respects `NO_COLOR=1` and auto-strips colors when piped
 - **Per-repo `.wt.toml` config** — override global settings (strategy, hooks, etc.) on a per-repository basis

docs/examples.md

@@ -60,6 +60,22 @@ pre_remove = [
 ]
 ```
 
+## Copy `.env` to new worktrees
+
+Automatically copy environment files from the main worktree so new branches are ready to run immediately:
+
+```toml
+[hooks]
+post_create = [
+  "test -f $WT_MAIN/.env && cp $WT_MAIN/.env $WT_PATH/.env || true"
+]
+post_checkout = [
+  "test -f $WT_MAIN/.env && cp $WT_MAIN/.env $WT_PATH/.env || true"
+]
+```
+
+This copies `.env` only if it exists in the main checkout. Extend the pattern for other config files (`.env.local`, `config/local.yml`, etc.) by adding more `cp` commands.
+
 ## Task spanning multiple repositories
 
 When a task or story requires changes across multiple repositories (e.g. a shared library and a main application), you can organize worktrees by feature instead of by repo using a custom pattern: