Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
docs: trim repeated explanations across six guides (#4575)
Maximilian Roosfc34f8e37568
diff --git a/docs/src/content/docs/config.md b/docs/src/content/docs/config.mdindex 731da1878..c063264ef 100644--- a/docs/src/content/docs/config.md+++ b/docs/src/content/docs/config.md@@ -1078,7 +1078,7 @@ $ wt config approvals list --format=json | jq -r .stateApproved commands are saved to `~/.config/worktrunk/approvals.toml`. Re-approval is required when the command template changes or the project moves.-`--yes` bypasses the prompt, and what it leaves behind depends on the command it is passed to. On a command that runs project commands it grants consent for that run alone and records nothing, so the next run asks again. On `wt config approvals add` the record is the whole point, so the approvals are written — which is how an unattended environment pre-approves a project it has just cloned.+`--yes` approves project commands for the current run without saving approval. `wt config approvals add --yes` saves approvals for future runs.### Reading approval statediff --git a/docs/src/content/docs/extending.md b/docs/src/content/docs/extending.mdindex 96d94749d..2383dbdd8 100644--- a/docs/src/content/docs/extending.md+++ b/docs/src/content/docs/extending.md@@ -4,15 +4,7 @@ description: "Three ways to add custom behavior: hooks for lifecycle automation,sidebar:order: 22----Worktrunk has three extension mechanisms.--**[Hooks](#hooks)** are shell commands that run automatically at lifecycle events (switching, starting, committing, merging, removing). Defined in TOML.--**[Aliases](#aliases)** are reusable shell commands invoked as `wt <name>`. Defined in TOML.--**[Custom subcommands](#custom-subcommands)** are standalone executables invoked as `wt <name>`. Drop `wt-foo` on `PATH` and it becomes `wt foo`.--| | Hooks | Aliases | Custom subcommands |+| | [Hooks](#hooks) | [Aliases](#aliases) | [Custom subcommands](#custom-subcommands) ||---|---|---|---|| **Trigger** | Automatic (lifecycle events) | Manual (`wt <name>`) | Manual (`wt <name>`) || **Defined in** | TOML config | TOML config | Any executable on `PATH` |diff --git a/docs/src/content/docs/llm-commits.md b/docs/src/content/docs/llm-commits.mdindex f748c3e1a..e598157a7 100644--- a/docs/src/content/docs/llm-commits.md+++ b/docs/src/content/docs/llm-commits.md@@ -205,7 +205,7 @@ See `wt config create --help` for the full default templates.## Appending to the prompt-`template-append` adds to the commit and squash prompts instead of replacing them. It lives in both user config (personal preferences) and project config (`.config/wt.toml`, shared so every teammate's LLM sees the same style guide). Each fragment is itself a [minijinja](https://docs.rs/minijinja/) template — Worktrunk renders it with the same variables as the main template (`{{ branch }}`, `{{ git_diff }}`, …), then appends the result after `<style>`. The user fragment renders into a `<user-guidance>` block and the project fragment into a `<project-guidance>` block, so the LLM can tell personal preference from shared convention:+`template-append` adds instructions to the default commit and squash prompts. Set it in user config for personal preferences or `.config/wt.toml` for shared project conventions. Fragments support the same template variables as the main prompt.```toml# .config/wt.toml@@ -216,7 +216,7 @@ template-append = """"""```-When both the user and project set `template-append`, the `<user-guidance>` block comes first, then `<project-guidance>`.+When both are configured, user instructions come before project instructions.The user fragment needs no approval — it's the developer's own config. For the project fragment, the first time the rendered text is sent to the LLM, Worktrunk shows the raw fragment in an approval prompt — the same one-shot gate as project-defined hooks. Subsequent commits don't re-prompt unless the fragment changes. Declining is non-fatal: the LLM runs with just the user fragment (if any).diff --git a/docs/src/content/docs/merge.md b/docs/src/content/docs/merge.mdindex cdf05a1b2..19b231767 100644--- a/docs/src/content/docs/merge.md+++ b/docs/src/content/docs/merge.md@@ -101,11 +101,7 @@ Use `--no-commit` to skip committing uncommitted changes and squashing; rebase s## Local CI-For personal projects, pre-merge hooks open up the possibility of a workflow with much faster iteration — an order of magnitude more small changes instead of fewer large ones.--Historically, ensuring tests ran before merging was difficult to enforce locally. Remote CI was valuable for the process as much as the checks: it guaranteed validation happened. `wt merge` brings that guarantee local.--The full workflow: start an agent (one of many) on a task, work elsewhere, return when it's ready. Review the diff, run `wt merge`, move on. Pre-merge hooks validate before merging — if they pass, the branch goes to the default branch and the worktree cleans up.+Pre-merge hooks run checks locally before merging. A failed check stops the merge:```toml# .config/wt.tomldiff --git a/docs/src/content/docs/shell-integration.md b/docs/src/content/docs/shell-integration.mdindex 3a5d99725..cd4753998 100644--- a/docs/src/content/docs/shell-integration.md+++ b/docs/src/content/docs/shell-integration.md@@ -75,17 +75,7 @@ wt switch feature # Now uses the dev build with shell integration### "Alias bypasses shell integration"-**Meaning**: An alias like `alias gwt="/usr/bin/wt"` or `alias gwt="wt.exe"` points directly to the binary instead of the shell function.--When shell integration is installed, it creates a shell function named `wt` (or `git-wt`). If the alias points to the binary path, it bypasses this function and shell integration won't work.--**Examples that bypass** (won't auto-cd):--```bash-alias gwt="/usr/bin/wt"-alias gwt="wt.exe"-alias wt="/path/to/wt"-```+**Meaning**: The alias invokes the binary directly, bypassing the shell function that changes directories.**Fix**: Change the alias to point to the function name instead of the binary:diff --git a/docs/src/content/docs/step.md b/docs/src/content/docs/step.mdindex 25517e089..a36a7a450 100644--- a/docs/src/content/docs/step.md+++ b/docs/src/content/docs/step.md@@ -992,14 +992,7 @@ Run a command; kill its whole process tree when its worktree is removed. Teardow### Why-A `post-start` hook to start a long-lived process and a `pre-remove` hook to-stop it is usually enough. But `pre-remove` only runs when worktrunk removes-the worktree, so a `git worktree remove`, an `rm -rf`, or a crashed hook skips-it. Across enough worktree churn some process is bound to outlive its worktree,-and with no cleanup these leaks accumulate (on macOS they eventually saturate-`fseventsd`). `tether` removes the need for a `pre-remove`: it ties the-command's lifetime to the worktree and kills the whole process group once the-worktree is gone.+`pre-remove` hooks run only when Worktrunk removes a worktree. `tether` also stops the command when another tool removes the worktree.### Argumentsdiff --git a/plugins/worktrunk/skills/worktrunk/reference/config.md b/plugins/worktrunk/skills/worktrunk/reference/config.mdindex 9bce97aa6..390a3cd53 100644--- a/plugins/worktrunk/skills/worktrunk/reference/config.md+++ b/plugins/worktrunk/skills/worktrunk/reference/config.md@@ -1070,7 +1070,7 @@ $ wt config approvals list --format=json | jq -r .stateApproved commands are saved to `~/.config/worktrunk/approvals.toml`. Re-approval is required when the command template changes or the project moves.-`--yes` bypasses the prompt, and what it leaves behind depends on the command it is passed to. On a command that runs project commands it grants consent for that run alone and records nothing, so the next run asks again. On `wt config approvals add` the record is the whole point, so the approvals are written — which is how an unattended environment pre-approves a project it has just cloned.+`--yes` approves project commands for the current run without saving approval. `wt config approvals add --yes` saves approvals for future runs.### Reading approval statediff --git a/plugins/worktrunk/skills/worktrunk/reference/extending.md b/plugins/worktrunk/skills/worktrunk/reference/extending.mdindex 5df28997f..d499c767e 100644--- a/plugins/worktrunk/skills/worktrunk/reference/extending.md+++ b/plugins/worktrunk/skills/worktrunk/reference/extending.md@@ -1,14 +1,6 @@# Extending Worktrunk-Worktrunk has three extension mechanisms.--**[Hooks](#hooks)** are shell commands that run automatically at lifecycle events (switching, starting, committing, merging, removing). Defined in TOML.--**[Aliases](#aliases)** are reusable shell commands invoked as `wt <name>`. Defined in TOML.--**[Custom subcommands](#custom-subcommands)** are standalone executables invoked as `wt <name>`. Drop `wt-foo` on `PATH` and it becomes `wt foo`.--| | Hooks | Aliases | Custom subcommands |+| | [Hooks](#hooks) | [Aliases](#aliases) | [Custom subcommands](#custom-subcommands) ||---|---|---|---|| **Trigger** | Automatic (lifecycle events) | Manual (`wt <name>`) | Manual (`wt <name>`) || **Defined in** | TOML config | TOML config | Any executable on `PATH` |diff --git a/plugins/worktrunk/skills/worktrunk/reference/llm-commits.md b/plugins/worktrunk/skills/worktrunk/reference/llm-commits.mdindex 8c748cd29..b27fb908a 100644--- a/plugins/worktrunk/skills/worktrunk/reference/llm-commits.md+++ b/plugins/worktrunk/skills/worktrunk/reference/llm-commits.md@@ -181,7 +181,7 @@ See `wt config create --help` for the full default templates.## Appending to the prompt-`template-append` adds to the commit and squash prompts instead of replacing them. It lives in both user config (personal preferences) and project config (`.config/wt.toml`, shared so every teammate's LLM sees the same style guide). Each fragment is itself a [minijinja](https://docs.rs/minijinja/) template — Worktrunk renders it with the same variables as the main template (`{{ branch }}`, `{{ git_diff }}`, …), then appends the result after `<style>`. The user fragment renders into a `<user-guidance>` block and the project fragment into a `<project-guidance>` block, so the LLM can tell personal preference from shared convention:+`template-append` adds instructions to the default commit and squash prompts. Set it in user config for personal preferences or `.config/wt.toml` for shared project conventions. Fragments support the same template variables as the main prompt.```toml# .config/wt.toml@@ -192,7 +192,7 @@ template-append = """"""```-When both the user and project set `template-append`, the `<user-guidance>` block comes first, then `<project-guidance>`.+When both are configured, user instructions come before project instructions.The user fragment needs no approval — it's the developer's own config. For the project fragment, the first time the rendered text is sent to the LLM, Worktrunk shows the raw fragment in an approval prompt — the same one-shot gate as project-defined hooks. Subsequent commits don't re-prompt unless the fragment changes. Declining is non-fatal: the LLM runs with just the user fragment (if any).diff --git a/plugins/worktrunk/skills/worktrunk/reference/merge.md b/plugins/worktrunk/skills/worktrunk/reference/merge.mdindex a6f2f6e88..d0a32da4b 100644--- a/plugins/worktrunk/skills/worktrunk/reference/merge.md+++ b/plugins/worktrunk/skills/worktrunk/reference/merge.md@@ -87,11 +87,7 @@ Use `--no-commit` to skip committing uncommitted changes and squashing; rebase s## Local CI-For personal projects, pre-merge hooks open up the possibility of a workflow with much faster iteration — an order of magnitude more small changes instead of fewer large ones.--Historically, ensuring tests ran before merging was difficult to enforce locally. Remote CI was valuable for the process as much as the checks: it guaranteed validation happened. `wt merge` brings that guarantee local.--The full workflow: start an agent (one of many) on a task, work elsewhere, return when it's ready. Review the diff, run `wt merge`, move on. Pre-merge hooks validate before merging — if they pass, the branch goes to the default branch and the worktree cleans up.+Pre-merge hooks run checks locally before merging. A failed check stops the merge:```toml# .config/wt.tomldiff --git a/plugins/worktrunk/skills/worktrunk/reference/shell-integration.md b/plugins/worktrunk/skills/worktrunk/reference/shell-integration.mdindex 296bec5d5..8b8c4abf0 100644--- a/plugins/worktrunk/skills/worktrunk/reference/shell-integration.md+++ b/plugins/worktrunk/skills/worktrunk/reference/shell-integration.md@@ -71,17 +71,7 @@ wt switch feature # Now uses the dev build with shell integration### "Alias bypasses shell integration"-**Meaning**: An alias like `alias gwt="/usr/bin/wt"` or `alias gwt="wt.exe"` points directly to the binary instead of the shell function.--When shell integration is installed, it creates a shell function named `wt` (or `git-wt`). If the alias points to the binary path, it bypasses this function and shell integration won't work.--**Examples that bypass** (won't auto-cd):--```bash-alias gwt="/usr/bin/wt"-alias gwt="wt.exe"-alias wt="/path/to/wt"-```+**Meaning**: The alias invokes the binary directly, bypassing the shell function that changes directories.**Fix**: Change the alias to point to the function name instead of the binary:diff --git a/plugins/worktrunk/skills/worktrunk/reference/step.md b/plugins/worktrunk/skills/worktrunk/reference/step.mdindex 684cf228c..dccbd4472 100644--- a/plugins/worktrunk/skills/worktrunk/reference/step.md+++ b/plugins/worktrunk/skills/worktrunk/reference/step.md@@ -980,14 +980,7 @@ Run a command; kill its whole process tree when its worktree is removed. Teardow### Why-A `post-start` hook to start a long-lived process and a `pre-remove` hook to-stop it is usually enough. But `pre-remove` only runs when worktrunk removes-the worktree, so a `git worktree remove`, an `rm -rf`, or a crashed hook skips-it. Across enough worktree churn some process is bound to outlive its worktree,-and with no cleanup these leaks accumulate (on macOS they eventually saturate-`fseventsd`). `tether` removes the need for a `pre-remove`: it ties the-command's lifetime to the worktree and kills the whole process group once the-worktree is gone.+`pre-remove` hooks run only when Worktrunk removes a worktree. `tether` also stops the command when another tool removes the worktree.### Argumentsdiff --git a/skills/worktrunk/reference/config.md b/skills/worktrunk/reference/config.mdindex 9bce97aa6..390a3cd53 100644--- a/skills/worktrunk/reference/config.md+++ b/skills/worktrunk/reference/config.md@@ -1070,7 +1070,7 @@ $ wt config approvals list --format=json | jq -r .stateApproved commands are saved to `~/.config/worktrunk/approvals.toml`. Re-approval is required when the command template changes or the project moves.-`--yes` bypasses the prompt, and what it leaves behind depends on the command it is passed to. On a command that runs project commands it grants consent for that run alone and records nothing, so the next run asks again. On `wt config approvals add` the record is the whole point, so the approvals are written — which is how an unattended environment pre-approves a project it has just cloned.+`--yes` approves project commands for the current run without saving approval. `wt config approvals add --yes` saves approvals for future runs.### Reading approval statediff --git a/skills/worktrunk/reference/extending.md b/skills/worktrunk/reference/extending.mdindex 5df28997f..d499c767e 100644--- a/skills/worktrunk/reference/extending.md+++ b/skills/worktrunk/reference/extending.md@@ -1,14 +1,6 @@# Extending Worktrunk-Worktrunk has three extension mechanisms.--**[Hooks](#hooks)** are shell commands that run automatically at lifecycle events (switching, starting, committing, merging, removing). Defined in TOML.--**[Aliases](#aliases)** are reusable shell commands invoked as `wt <name>`. Defined in TOML.--**[Custom subcommands](#custom-subcommands)** are standalone executables invoked as `wt <name>`. Drop `wt-foo` on `PATH` and it becomes `wt foo`.--| | Hooks | Aliases | Custom subcommands |+| | [Hooks](#hooks) | [Aliases](#aliases) | [Custom subcommands](#custom-subcommands) ||---|---|---|---|| **Trigger** | Automatic (lifecycle events) | Manual (`wt <name>`) | Manual (`wt <name>`) || **Defined in** | TOML config | TOML config | Any executable on `PATH` |diff --git a/skills/worktrunk/reference/llm-commits.md b/skills/worktrunk/reference/llm-commits.mdindex 8c748cd29..b27fb908a 100644--- a/skills/worktrunk/reference/llm-commits.md+++ b/skills/worktrunk/reference/llm-commits.md@@ -181,7 +181,7 @@ See `wt config create --help` for the full default templates.## Appending to the prompt-`template-append` adds to the commit and squash prompts instead of replacing them. It lives in both user config (personal preferences) and project config (`.config/wt.toml`, shared so every teammate's LLM sees the same style guide). Each fragment is itself a [minijinja](https://docs.rs/minijinja/) template — Worktrunk renders it with the same variables as the main template (`{{ branch }}`, `{{ git_diff }}`, …), then appends the result after `<style>`. The user fragment renders into a `<user-guidance>` block and the project fragment into a `<project-guidance>` block, so the LLM can tell personal preference from shared convention:+`template-append` adds instructions to the default commit and squash prompts. Set it in user config for personal preferences or `.config/wt.toml` for shared project conventions. Fragments support the same template variables as the main prompt.```toml# .config/wt.toml@@ -192,7 +192,7 @@ template-append = """"""```-When both the user and project set `template-append`, the `<user-guidance>` block comes first, then `<project-guidance>`.+When both are configured, user instructions come before project instructions.The user fragment needs no approval — it's the developer's own config. For the project fragment, the first time the rendered text is sent to the LLM, Worktrunk shows the raw fragment in an approval prompt — the same one-shot gate as project-defined hooks. Subsequent commits don't re-prompt unless the fragment changes. Declining is non-fatal: the LLM runs with just the user fragment (if any).diff --git a/skills/worktrunk/reference/merge.md b/skills/worktrunk/reference/merge.mdindex a6f2f6e88..d0a32da4b 100644--- a/skills/worktrunk/reference/merge.md+++ b/skills/worktrunk/reference/merge.md@@ -87,11 +87,7 @@ Use `--no-commit` to skip committing uncommitted changes and squashing; rebase s## Local CI-For personal projects, pre-merge hooks open up the possibility of a workflow with much faster iteration — an order of magnitude more small changes instead of fewer large ones.--Historically, ensuring tests ran before merging was difficult to enforce locally. Remote CI was valuable for the process as much as the checks: it guaranteed validation happened. `wt merge` brings that guarantee local.--The full workflow: start an agent (one of many) on a task, work elsewhere, return when it's ready. Review the diff, run `wt merge`, move on. Pre-merge hooks validate before merging — if they pass, the branch goes to the default branch and the worktree cleans up.+Pre-merge hooks run checks locally before merging. A failed check stops the merge:```toml# .config/wt.tomldiff --git a/skills/worktrunk/reference/shell-integration.md b/skills/worktrunk/reference/shell-integration.mdindex 296bec5d5..8b8c4abf0 100644--- a/skills/worktrunk/reference/shell-integration.md+++ b/skills/worktrunk/reference/shell-integration.md@@ -71,17 +71,7 @@ wt switch feature # Now uses the dev build with shell integration### "Alias bypasses shell integration"-**Meaning**: An alias like `alias gwt="/usr/bin/wt"` or `alias gwt="wt.exe"` points directly to the binary instead of the shell function.--When shell integration is installed, it creates a shell function named `wt` (or `git-wt`). If the alias points to the binary path, it bypasses this function and shell integration won't work.--**Examples that bypass** (won't auto-cd):--```bash-alias gwt="/usr/bin/wt"-alias gwt="wt.exe"-alias wt="/path/to/wt"-```+**Meaning**: The alias invokes the binary directly, bypassing the shell function that changes directories.**Fix**: Change the alias to point to the function name instead of the binary:diff --git a/skills/worktrunk/reference/step.md b/skills/worktrunk/reference/step.mdindex 684cf228c..dccbd4472 100644--- a/skills/worktrunk/reference/step.md+++ b/skills/worktrunk/reference/step.md@@ -980,14 +980,7 @@ Run a command; kill its whole process tree when its worktree is removed. Teardow### Why-A `post-start` hook to start a long-lived process and a `pre-remove` hook to-stop it is usually enough. But `pre-remove` only runs when worktrunk removes-the worktree, so a `git worktree remove`, an `rm -rf`, or a crashed hook skips-it. Across enough worktree churn some process is bound to outlive its worktree,-and with no cleanup these leaks accumulate (on macOS they eventually saturate-`fseventsd`). `tether` removes the need for a `pre-remove`: it ties the-command's lifetime to the worktree and kills the whole process group once the-worktree is gone.+`pre-remove` hooks run only when Worktrunk removes a worktree. `tether` also stops the command when another tool removes the worktree.### Argumentsdiff --git a/src/cli/config.rs b/src/cli/config.rsindex 11991bffc..7fc8b09be 100644--- a/src/cli/config.rs+++ b/src/cli/config.rs@@ -793,7 +793,7 @@ $ wt config approvals list --format=json | jq -r .stateApproved commands are saved to `~/.config/worktrunk/approvals.toml`. Re-approval is required when the command template changes or the project moves.-`--yes` bypasses the prompt, and what it leaves behind depends on the command it is passed to. On a command that runs project commands it grants consent for that run alone and records nothing, so the next run asks again. On `wt config approvals add` the record is the whole point, so the approvals are written — which is how an unattended environment pre-approves a project it has just cloned.+`--yes` approves project commands for the current run without saving approval. `wt config approvals add --yes` saves approvals for future runs.## Reading approval statediff --git a/src/cli/mod.rs b/src/cli/mod.rsindex 3bea63816..799e8d211 100644--- a/src/cli/mod.rs+++ b/src/cli/mod.rs@@ -1535,11 +1535,7 @@ Use `--no-commit` to skip committing uncommitted changes and squashing; rebase s## Local CI-For personal projects, pre-merge hooks open up the possibility of a workflow with much faster iteration — an order of magnitude more small changes instead of fewer large ones.--Historically, ensuring tests ran before merging was difficult to enforce locally. Remote CI was valuable for the process as much as the checks: it guaranteed validation happened. `wt merge` brings that guarantee local.--The full workflow: start an agent (one of many) on a task, work elsewhere, return when it's ready. Review the diff, run `wt merge`, move on. Pre-merge hooks validate before merging — if they pass, the branch goes to the default branch and the worktree cleans up.+Pre-merge hooks run checks locally before merging. A failed check stops the merge:```toml# .config/wt.tomldiff --git a/src/cli/step.rs b/src/cli/step.rsindex 2622a7757..c99e05623 100644--- a/src/cli/step.rs+++ b/src/cli/step.rs@@ -766,14 +766,7 @@ refuses), unless `--commit` is passed./// Teardown is automatic and needs no `pre-remove` hook; the group gets `SIGTERM` then `SIGKILL`.#[command(after_long_help = r#"## Why-A `post-start` hook to start a long-lived process and a `pre-remove` hook to-stop it is usually enough. But `pre-remove` only runs when worktrunk removes-the worktree, so a `git worktree remove`, an `rm -rf`, or a crashed hook skips-it. Across enough worktree churn some process is bound to outlive its worktree,-and with no cleanup these leaks accumulate (on macOS they eventually saturate-`fseventsd`). `tether` removes the need for a `pre-remove`: it ties the-command's lifetime to the worktree and kills the whole process group once the-worktree is gone.+`pre-remove` hooks run only when Worktrunk removes a worktree. `tether` also stops the command when another tool removes the worktree.## Argumentsdiff --git a/tests/snapshots/integration__integration_tests__help__help_config_approvals.snap b/tests/snapshots/integration__integration_tests__help__help_config_approvals.snapindex c661bd3ad..c8688a9d5 100644--- a/tests/snapshots/integration__integration_tests__help__help_config_approvals.snap+++ b/tests/snapshots/integration__integration_tests__help__help_config_approvals.snap@@ -101,7 +101,7 @@ Check whether an unattended run would stop for approval:Approved commands are saved to [2m~/.config/worktrunk/approvals.toml[0m. Re-approval is required when the command template changes or the project moves.-[2m--yes[0m bypasses the prompt, and what it leaves behind depends on the command it is passed to. On a command that runs project commands it grants consent for that run alone and records nothing, so the next run asks again. On [2mwt config approvals add[0m the record is the whole point, so the approvals are written — which is how an unattended environment pre-approves a project it has just cloned.+[2m--yes[0m approves project commands for the current run without saving approval. [2mwt config approvals add --yes[0m saves approvals for future runs.[1m[32mReading approval state[0mdiff --git a/tests/snapshots/integration__integration_tests__help__help_md_merge.snap b/tests/snapshots/integration__integration_tests__help__help_md_merge.snapindex 2f37c9808..a530abe33 100644--- a/tests/snapshots/integration__integration_tests__help__help_md_merge.snap+++ b/tests/snapshots/integration__integration_tests__help__help_md_merge.snap@@ -199,11 +199,7 @@ Use `--no-commit` to skip committing uncommitted changes and squashing; rebase s## Local CI-For personal projects, pre-merge hooks open up the possibility of a workflow with much faster iteration — an order of magnitude more small changes instead of fewer large ones.--Historically, ensuring tests ran before merging was difficult to enforce locally. Remote CI was valuable for the process as much as the checks: it guaranteed validation happened. `wt merge` brings that guarantee local.--The full workflow: start an agent (one of many) on a task, work elsewhere, return when it's ready. Review the diff, run `wt merge`, move on. Pre-merge hooks validate before merging — if they pass, the branch goes to the default branch and the worktree cleans up.+Pre-merge hooks run checks locally before merging. A failed check stops the merge:```toml# .config/wt.tomldiff --git a/tests/snapshots/integration__integration_tests__help__help_merge_long.snap b/tests/snapshots/integration__integration_tests__help__help_merge_long.snapindex 175ef531e..f2dd07ce1 100644--- a/tests/snapshots/integration__integration_tests__help__help_merge_long.snap+++ b/tests/snapshots/integration__integration_tests__help__help_merge_long.snap@@ -181,11 +181,7 @@ Use [2m--no-commit[0m to skip committing uncommitted changes and squashing; re[1m[32mLocal CI[0m-For personal projects, pre-merge hooks open up the possibility of a workflow with much faster iteration — an order of magnitude more small changes instead of fewer large ones.--Historically, ensuring tests ran before merging was difficult to enforce locally. Remote CI was valuable for the process as much as the checks: it guaranteed validation happened. [2mwt merge[0m brings that guarantee local.--The full workflow: start an agent (one of many) on a task, work elsewhere, return when it's ready. Review the diff, run [2mwt merge[0m, move on. Pre-merge hooks validate before merging — if they pass, the branch goes to the default branch and the worktree cleans up.+Pre-merge hooks run checks locally before merging. A failed check stops the merge:[107m [0m [2m# .config/wt.toml[0m[107m [0m [2m[36m[[pre-merge]][0m