Completions and Pi integration
Zsh completions
Section titled “Zsh completions”mkdir -p ~/.zfuncshirei completions zsh > ~/.zfunc/_shireifpath=(~/.zfunc $fpath)Ensure compinit runs after adding the directory to fpath.
Fish completions
Section titled “Fish completions”mkdir -p ~/.config/fish/completionsshirei completions fish > ~/.config/fish/completions/shirei.fishBash completions
Section titled “Bash completions”Source generated completions from your shell configuration:
source <(shirei completions bash)Elvish and PowerShell are also accepted by shirei completions.
Pi extension and skill
Section titled “Pi extension and skill”The Shirei source repository includes:
integrations/pi/shirei.ts: a/shireicommand extension.integrations/pi/skills/shirei/SKILL.md: operational guidance for agents.
Install both:
mkdir -p ~/.pi/agent/extensions ~/.agents/skills/shireicp integrations/pi/shirei.ts ~/.pi/agent/extensions/shirei.tscp integrations/pi/skills/shirei/SKILL.md ~/.agents/skills/shirei/SKILL.mdRun /reload in Pi, then use:
/shirei branch feature/name/shirei branch feature/name --base main/shirei recent/shirei sessions/shirei worktrees/shirei worktrees unfinished/shirei worktrees scanCommand reports use pi.appendEntry() and do not enter LLM context. The extension blocks /shirei worktrees prune because pruning requires an interactive terminal. Branch commands also require Pi to run inside tmux or Herdr.
Recommended terminal bindings
Section titled “Recommended terminal bindings”bind-key -r f run-shell "tmux neww shirei"[[keys.command]]key = "prefix+f"type = "pane"command = "shirei"Shell completion scripts cover commands, subcommands, and options. They do not dynamically complete Git branches; use shirei branch without a name for the interactive branch picker.