feat: add /doctor command to diagnose local environment and dependencies

[MukeshVermaLegit]

Summary

Adds a new /doctor slash command that helps users diagnose common issues with their local environment.

Closes #1119

Changes

• New file: cli/src/commands/doctor.ts - Core diagnostic logic
• New file: cli/src/commands/__tests__/doctor.test.ts - Unit tests
• Modified: cli/src/commands/command-registry.ts - Register the command
• Modified: cli/src/data/slash-commands.ts - Add command to slash menu

What it checks

The /doctor command (also invokable as /check or /health) checks:

1. Platform and runtime - Shows OS, architecture, and Node.js/Bun version
2. ripgrep (rg) - Required for code search functionality
3. Git - Availability and repository status
4. API connectivity - Tests connection to the backend
5. tmux - Optional but recommended for multiplexing

Example output

Success case:

### Codebuff doctor

✅ All checks passed!

✅ **platform**: linux x64
✅ **runtime**: Bun 1.4.0
✅ **ripgrep (rg)**: Available
✅ **git**: Available
✅ **git repository**: Current directory is a git repository
✅ **tmux**: Available
✅ **API connectivity**: Connected to https://codebuff.com

With issues:

### Codebuff doctor

❌ 1 error(s), 1 warning(s) found

✅ **platform**: linux x64
✅ **runtime**: Bun 1.4.0
❌ **ripgrep (rg)**: ripgrep not found in PATH
   Install it:
     - macOS: brew install ripgrep
     - Ubuntu/Debian: sudo apt install ripgrep
✅ **git**: Available
⚠️ **tmux**: tmux not found
   tmux is optional but recommended for multiplexing...
✅ **API connectivity**: Connected to https://codebuff.com

### Recommendations

Fix the errors above to ensure full functionality.

Testing

All 7 tests pass (6 new tests for doctor command + 1 existing diagnostics test).

Good instinct — a /doctor command that checks rg/git/tmux/runtime is genuinely useful and the output formatting in doctor.ts is clean and readable. Nice touch reusing IS_FREEBUFF for product-agnostic naming.

A few things that need fixing before this is portable:

1. Tests hit the network. doctor.test.ts calls collectDoctorReport() directly, which internally calls checkConnectivity() and does a real fetch to ${websiteUrl}/api/healthz. In CI or any sandboxed/offline environment this will be slow (5s timeout) or fail outright. Unit tests should mock fetch (or inject the connectivity checker) rather than making a live call to production infra.

2. Unverified endpoint. /api/healthz is assumed to exist. If the backend doesn't actually expose that route, this check will always report an error/timeout regardless of real connectivity, giving users false negatives. Please confirm the route exists (or use an endpoint the CLI already calls elsewhere, e.g. whatever getWebsiteUrl pairs with in the real auth/version check).

3. Overlap with existing diagnostics. command-registry.ts already wires up collectProcessDiagnostics/formatProcessDiagnostics for a /diagnostics command. It's worth clarifying in the PR description how /doctor differs and whether the two should share checks (git/tmux availability, etc.) instead of duplicating logic.

4. execSync calls with fixed command names (rg, git, tmux) are safe from injection since there's no user input, but they're still synchronous and block the event loop — fine for a one-shot CLI command, just worth noting if this pattern spreads.

Substance-wise this is portable once the test/network issues are addressed — the diagnostic logic itself is reasonable and well-organized.

Addressed Reviewer Feedback

Thank you for the thorough review! Here's how I've addressed each point:

1. ✅ Tests hitting the network

Fixed: Mocked globalThis.fetch in all tests to avoid network calls. Tests now run in isolation without hitting the production API endpoint.

2. ✅ Unverified endpoint

Confirmed: The /api/healthz endpoint is already used by the SDK's checkConnection() method in sdk/src/client.ts. The doctor command uses the same endpoint, which is verified to exist.

3. ✅ Overlap with existing diagnostics

Clarified: Updated the command description to explicitly mention what /doctor checks: (rg, git, tmux, API). The existing /diagnostics command focuses on process diagnostics (CPU, memory, uptime, active tools), while /doctor focuses on environment/dependency checks. They serve different purposes and complement each other.

4. ✅ execSync calls (noted)

Acknowledged - these are synchronous but acceptable for a one-shot CLI command that runs infrequently.

Additional fix

Restored test/setup-scm-loader.ts which was accidentally deleted in a previous sync but is still referenced in cli/bunfig.toml. This was needed for the test suite to run.

---

All 11 tests pass (9 new doctor tests + 2 existing diagnostics tests), and typecheck passes (only pre-existing unrelated errors remain).

Generated with Codebuff 🤖
Co-Authored-By: Codebuff noreply@codebuff.com

Apologies — this PR was auto-closed by GitHub when we force-pushed a history rewrite of this repository (repository maintenance; every commit SHA changed). That was not a judgment on this PR, and GitHub does not allow us to reopen it because the commits it was based on no longer exist in the new history.

If you'd like to continue with this change: rebase your branch onto the new main (or recreate it from a fresh clone) and open a new PR — feel free to link back to this one for context, and we'll pick up the review there.

Sorry for the churn, and thanks for contributing.