Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

docs: link worktrunk-sync in Extending and FAQ (#2225)

Worktrunk Bot9884cdcf864e
diff --git a/docs/content/extending.md b/docs/content/extending.md
index 051c131e4..54b32184d 100644
--- a/docs/content/extending.md
+++ b/docs/content/extending.md
@@ -188,3 +188,7 @@ Any executable named `wt-<name>` on `PATH` becomes available as `wt <name>` —
Arguments pass through verbatim, stdio is inherited, and the child's exit code propagates unchanged. External subcommands don't have access to template variables.
If nothing matches — no built-in, no nested subcommand, no `wt-<name>` on `PATH` — wt prints a "not a wt command" error with a typo suggestion.
+
+### Examples
+
+- [`worktrunk-sync`](https://github.com/pablospe/worktrunk-sync) — rebases stacked worktree branches in dependency order, inferring the tree from git history. Install with `cargo install worktrunk-sync`, then run as `wt sync`.
diff --git a/docs/content/faq.md b/docs/content/faq.md
index 1caab8a0c..afe3efb77 100644
--- a/docs/content/faq.md
+++ b/docs/content/faq.md
@@ -58,6 +58,10 @@ These tools can be used together—run git-machete or git-town inside individual
Git TUIs operate on a single repository. Worktrunk manages multiple worktrees, runs automation hooks, and aggregates status across branches. TUIs work inside each worktree directory.
+## Does Worktrunk support stacked branches?
+
+Not natively — stacked-branch workflows are a large design space, so Worktrunk treats them as an extension rather than a built-in. [`worktrunk-sync`](https://github.com/pablospe/worktrunk-sync) is a community tool that auto-detects the branch dependency tree from git history and rebases each branch onto its parent in topological order. Install with `cargo install worktrunk-sync` and run as `wt sync` (via [external subcommands](@/extending.md#external-subcommands)).
+
## There's an issue with my shell setup
If shell integration isn't working (auto-cd not happening, completions missing, `wt` not found as a function), the fastest path to a fix is using Claude Code with the Worktrunk plugin:
diff --git a/skills/worktrunk/reference/extending.md b/skills/worktrunk/reference/extending.md
index 616f228e4..c243434ab 100644
--- a/skills/worktrunk/reference/extending.md
+++ b/skills/worktrunk/reference/extending.md
@@ -188,3 +188,7 @@ wt -C /tmp/repo sync # -C is forwarded as the child's working directory
Arguments pass through verbatim, stdio is inherited, and the child's exit code propagates unchanged. External subcommands don't have access to template variables.
If nothing matches — no built-in, no nested subcommand, no `wt-<name>` on `PATH` — wt prints a "not a wt command" error with a typo suggestion.
+
+### Examples
+
+- [`worktrunk-sync`](https://github.com/pablospe/worktrunk-sync) — rebases stacked worktree branches in dependency order, inferring the tree from git history. Install with `cargo install worktrunk-sync`, then run as `wt sync`.
diff --git a/skills/worktrunk/reference/faq.md b/skills/worktrunk/reference/faq.md
index 35daa0961..93636e47e 100644
--- a/skills/worktrunk/reference/faq.md
+++ b/skills/worktrunk/reference/faq.md
@@ -51,6 +51,10 @@ These tools can be used together—run git-machete or git-town inside individual
Git TUIs operate on a single repository. Worktrunk manages multiple worktrees, runs automation hooks, and aggregates status across branches. TUIs work inside each worktree directory.
+## Does Worktrunk support stacked branches?
+
+Not natively — stacked-branch workflows are a large design space, so Worktrunk treats them as an extension rather than a built-in. [`worktrunk-sync`](https://github.com/pablospe/worktrunk-sync) is a community tool that auto-detects the branch dependency tree from git history and rebases each branch onto its parent in topological order. Install with `cargo install worktrunk-sync` and run as `wt sync` (via [external subcommands](https://worktrunk.dev/extending/#external-subcommands)).
+
## There's an issue with my shell setup
If shell integration isn't working (auto-cd not happening, completions missing, `wt` not found as a function), the fastest path to a fix is using Claude Code with the Worktrunk plugin: