Summary
The CLI exposes a --completions flag (or a completions subcommand) for shell completion script generation, but it is not advertised in --help, not mentioned in USER_GUIDE.md, and the install path / per-shell coverage (bash/zsh/fish/powershell) is unclear. Users who would benefit (heavy shell users) cannot discover it.
Where
src/CodeIndex/Cli/ProgramRunner.cs (completion entry point)USER_GUIDE.md (no completion install instructions)
Suggested approach
(1) Add a top-level "Shell completions" section to USER_GUIDE.md with one-liner install commands per shell. (2) Document supported shells explicitly. (3) Surface the flag in --help output. (4) If only bash is currently supported, file follow-up work for zsh/fish/pwsh.
Summary
The CLI exposes a
--completionsflag (or acompletionssubcommand) for shell completion script generation, but it is not advertised in--help, not mentioned inUSER_GUIDE.md, and the install path / per-shell coverage (bash/zsh/fish/powershell) is unclear. Users who would benefit (heavy shell users) cannot discover it.Where
src/CodeIndex/Cli/ProgramRunner.cs(completion entry point)USER_GUIDE.md(no completion install instructions)Suggested approach
(1) Add a top-level "Shell completions" section to
USER_GUIDE.mdwith one-liner install commands per shell. (2) Document supported shells explicitly. (3) Surface the flag in--helpoutput. (4) If only bash is currently supported, file follow-up work for zsh/fish/pwsh.