feat: add bootcamp completion for bash/zsh/fish (#54)

Adds `bootcamp completion <shell>` which prints a tab-completion script for
bash, zsh, or fish. The completion spec (subcommands, aliases, and option
flags) is collected from the live Commander `program` at runtime, so the
scripts always match the real CLI surface and never drift as commands are
added or changed.

- src/completion.ts: pure, fully-testable spec collection + per-shell renderers
- src/commands/completion-command.ts: validation, exit codes, injectable IO
- Generated bash script validated with `bash -n` and a functional COMPREPLY check

Tests: 17 unit (spec + renderers), 4 wrapper unit (validation/DI), 4 E2E
spawning the real CLI for each shell + the unsupported-shell error path.

Co-authored-by: Arthur742Ramos <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Author: 3 people

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- `bootcamp completion <bash|zsh|fish>` command to print a shell completion script for tab-completing subcommands, their aliases, and option flags. The completion data is derived from the live CLI definition, so it can never drift from the actual command surface; pipe it to your shell's completion directory (or `source <(bootcamp completion bash)`).
 - `bootcamp styles` command (alias `style`) to list the built-in style packs and the documentation sections each one enables, so users can choose a `--style` without reading the source. Prints a per-pack summary (tone, depth, emoji, first-task count, enabled sections) plus a section-coverage matrix, flags the default pack (`oss`), and supports `--json` for scripting.
 - `bootcamp init` command to scaffold a `.bootcamprc.json` configuration file in the current directory. Refuses to overwrite an existing config unless `--force`, supports `--print` to preview the config on stdout without writing, `--path` for a custom output location, and `--style` to preset a built-in style pack.
 - `bootcamp health <repo-url>` command: a standalone, deterministic onboarding-readiness score for any repository (local path or remote URL) without invoking the LLM. Prints a human-readable report by default, supports `--json` for scripting, and offers a CI gate via `--check`/`--min-score` (exits non-zero when the score falls below the threshold). Reuses the same `computeRepoHealth` engine that powers `HEALTH.md`.

README.md

@@ -145,8 +145,8 @@ Onboarding Risk: 18/100 (A) 🟢
 | GitHub stars | 29 |
 | Generated files | 14+ |
 | Test suite | 1,000+ tests |
-| Source files | 48 TypeScript modules |
-| Test files | 70 Vitest files |
+| Source files | 50 TypeScript modules |
+| Test files | 73 Vitest files |
 | Lines of code | 13,381 TypeScript LOC (src/) |
 | Languages supported | 10+ |
 | Generation time | < 60 seconds |
@@ -583,6 +583,7 @@ npm install -g @mermaid-js/mermaid-cli
 | `bootcamp init` | Scaffold a `.bootcamprc.json` config (`--force`, `--print`, `--style`) |
 | `bootcamp styles` | List the built-in style packs and the sections each enables (`--json`) |
 | `bootcamp doctor` | Diagnose your environment (`--json`) |
+| `bootcamp completion <shell>` | Print a shell completion script (bash, zsh, fish) |
 | `bootcamp cache list\|prune\|clear` | Manage the analysis cache |
 
 ## Programmatic API

src/cli.ts

@@ -24,6 +24,7 @@ import { pathToFileURL } from "url";
 import { clearCache, getCacheDir, pruneCache } from "./cache.js";
 import { runAskCommand } from "./commands/ask-command.js";
 import { runCacheList } from "./commands/cache-list.js";
+import { runCompletionCommand } from "./commands/completion-command.js";
 import { runPullRequestDiff } from "./commands/diff-command.js";
 import { runDocsCommand } from "./commands/docs-command.js";
 import { runDoctor } from "./commands/doctor-command.js";
@@ -403,6 +404,13 @@ program
     runStylesCommand({ json: opts.json });
   });
 
+program
+  .command("completion <shell>")
+  .description("Print a shell completion script (bash, zsh, or fish)")
+  .action((shell: string) => {
+    runCompletionCommand(program, { shell });
+  });
+
 const cacheCommand = program
   .command("cache")
   .description("Manage the analysis cache");

src/commands/completion-command.ts

@@ -0,0 +1,64 @@
+/**
+ * `bootcamp completion <shell>` command.
+ *
+ * Prints a shell completion script (bash/zsh/fish) to stdout, derived from the
+ * live Commander program so it always matches the real command surface. This
+ * module handles validation and process wiring; the script generation lives in
+ * `src/completion.ts`. Dependencies are injectable for unit testing.
+ */
+
+import chalk from "chalk";
+import type { Command } from "commander";
+
+import {
+  collectCompletionSpec,
+  isSupportedShell,
+  renderCompletion,
+  SUPPORTED_SHELLS,
+} from "../completion.js";
+
+export interface CompletionCommandOptions {
+  shell?: string;
+}
+
+export interface CompletionCommandDeps {
+  log?: (message: string) => void;
+  error?: (message: string) => void;
+  exit?: (code: number) => void;
+}
+
+/**
+ * Run the `completion` command against a configured `program`.
+ *
+ * Prints the requested shell's completion script to stdout. On an unknown or
+ * missing shell, writes an error to stderr and exits non-zero.
+ */
+export function runCompletionCommand(
+  program: Command,
+  options: CompletionCommandOptions,
+  deps: CompletionCommandDeps = {}
+): void {
+  const log = deps.log ?? ((msg: string) => console.log(msg));
+  const error = deps.error ?? ((msg: string) => console.error(msg));
+  const exit = deps.exit ?? ((code: number) => process.exit(code));
+
+  const shell = (options.shell ?? "").toLowerCase();
+
+  if (!shell) {
+    error(chalk.red(`Missing shell. Choose one of: ${SUPPORTED_SHELLS.join(", ")}`));
+    exit(1);
+    return;
+  }
+
+  if (!isSupportedShell(shell)) {
+    error(
+      chalk.red(`Unsupported shell: ${shell}.`) +
+        chalk.dim(` Choose one of: ${SUPPORTED_SHELLS.join(", ")}`)
+    );
+    exit(1);
+    return;
+  }
+
+  const spec = collectCompletionSpec(program);
+  log(renderCompletion(shell, spec));
+}