empire-git

Render the canonical PR description body. Use whenever drafting, writing, updating, refreshing, or regenerating a "PR description", "PR body", "pull request description", "pull request body", "PR summary", "PR template", "GitHub PR body", or any text destined for `gh pr create --body`, `gh pr create --body-file`, `gh pr edit --body`, `gh pr edit --body-file`, or a GitHub PR template. Triggers on phrases like "draft a PR", "write the PR", "summarize this branch for review", "regenerate PR body". MUST be invoked before any `gh pr create --body*` or `gh pr edit --body*` per the empire-git rules. Output is markdown ready to pipe to stdin.

Batch cleanup across MULTIPLE stale worktrees and orphaned branches. Use this when the user wants to tidy up accumulated worktrees, asks about old branches, mentions cleaning up their workspace, says "stale worktrees", "orphan branches", "prune worktrees", "clean up old branches", "purge stale worktrees", or "housekeeping". For finishing ONE specific worktree, use worktree-close instead. Also triggers for `/empire-git:worktree-cleanup [--dry-run] [--days N]`.

Finish work in a SINGLE worktree — push, remove the worktree, and optionally delete the branch. Use this when the user is done with a specific worktree, wants to wrap one up, push and move on, or no longer needs a parallel environment. Triggers on phrases like "close this worktree", "I'm done with this worktree", "wrap up this branch", "push and remove", "tear down this worktree". For batch cleanup of MULTIPLE stale worktrees, use worktree-cleanup instead. Also triggers for `/empire-git:worktree-close [branch] [--push] [--discard] [--force]`.

Answer questions about the worktree toolkit — VSCode integration, gitignore, port offsets, env files, dependency installs, workflow tips. Use when the user asks how worktrees work, "how do I open this in VSCode", "why is .env copied", "what about port collisions", "how do worktrees affect main repo", "worktree workflow", "show me the worktree FAQ", or any question about the setup. Also triggers for `/empire-git:worktree-help [question]`.

Read-only inventory of active worktrees with branch, status, sync state, and staleness info. Use this when the user asks what worktrees exist, "list worktrees", "show my worktrees", "what's in flight", "which branches have worktrees", "stale worktrees", "any forgotten worktrees", or wants a parallel-work overview. Reports state only — never deletes or modifies. For removal use worktree-close (single) or worktree-cleanup (batch). Also triggers for `/empire-git:worktree-list [--stale]`.

Fold ONE worktree's branch INTO another branch using git merge. Use this when the user wants to combine a worktree branch into a parent branch, batch small fixes into one branch before opening a single PR, or fold sub-feature branches back together. Triggers on phrases like "merge this worktree into X", "fold sub-branches back", "combine worktree branches", "merge feat/X into main locally". This is always a real `git merge` and defaults to `--no-ff`. For pushing to remote, use `worktree-close --push` instead. For batch teardown of stale worktrees, use worktree-cleanup. Also triggers for `/empire-git:worktree-merge [branch] --into <target> [--no-close] [--ff]`.

Create or reopen a git worktree for parallel development. Use whenever the user wants to "open a worktree", "spin up a branch", "work on X separately", "work on this in parallel", "start a parallel task", "isolated environment for an agent", "side branch without switching", or mentions worktrees, parallel branches, or stacked work. Also triggers for `/empire-git:worktree-open [branch | task description] [--base <branch>]`.