Installation · inspect by default
/doctor
Diagnose installation and configuration problems
Use to diagnose installed toolkit state; setup intentionally changes installation.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select doctor from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv doctor, /just-vibe doctor and /jv:doctor in Claude. See shortcut setup and context examples.
/just-vibe:doctor Check the Claude project-scope just-vibe installation without changing it./just-vibe:doctor Diagnose a disabled plugin with a newer payload than the native cache./just-vibe:doctor Inspect prerequisites when the host executable is missing; do not install it implicitly.What the agent does
- Resolve the bundled installer, then run its doctor operation for the requested host, source and Claude scope. Infer the active host only when unambiguous; --local means a complete persistent source checkout.
- Report actual prerequisite, marketplace, installation and enablement results. Do not run setup/update or edit configuration to make a status question pass. Unknown inventory formats and conflicts remain actionable blockers.
- Separate package presence, native registration, enabled state and actual version. The installer reports every failing layer at once; recommend repairs that cover exactly the observed failing layers.
- Claude shortcut health (commands/jv.md, commands/just-vibe.md and the jv skills plugin) is a separate layer from native registration; report it separately.
Inputs
- just-vibe host, installation source, and scope. Requires host CLI discovery.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Installation/configuration diagnosis; repairs go through an explicitly requested setup/update operation.
- Writes
- No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.
- Mode
- Inspect; just-vibe host, installation source, and scope. Requires host CLI discovery.
- Prerequisites
- Node.js 22+. Codex and Claude targets also need the host CLI with native plugin support; editor adapters need only the project directory. Git is required only for --github. Use the bundled installer; preserve marketplace and scope checks.
Expected output
- Status, evidence, and exact remedy for each diagnosed problem.
- Host/scope/source/version observations and remedies with unverified states explicit.
How the work is checked
- Disabled and absent plugins are distinguished; an unexpected marketplace source blocks a healthy result.
When to stop or clarify
- Unknown host output is not guessed. Never delete caches or edit global configuration as an automatic diagnostic step.
Handling missing context
- Infer
- Inspect selected host, native CLI support, existing source/scope and package version without changing global configuration.
- Assume
- Use the documented bundled source and existing host conventions unless the user selects another source.
- Ask
- Ask only when multiple host/scope/source choices cannot be resolved from context and would change installation; report an actual missing executable instead of requesting unrelated credentials.
Technical guidance
- Evidence
- Inspect selected host, source/scope, native inventory, enabled state, payload version and supported CLI commands.
- Method
- Distinguish absent, disabled, conflicting source and stale cached payload using read-only evidence.
- Pitfall
- Finding an executable or directory does not prove the plugin is enabled or the current session loaded its latest skills.
- Check
- Report exact observed status and a target-specific repair; diagnose must not silently become install/update or cache deletion.
Situational decisions
When wrapper reports success but host cache is stale: Report the mismatch and exact update/check sequence; do not call the installation healthy.
When installation is healthy but automatic assistance does not activate: Run diagnose status --root <project>, then assist status, and report the first unobserved stage (hook received, workflow selected, workflow loaded, tools observed) and the host hook-trust step.
When the target is an editor adapter: Run doctor with --root <project> and report the adapter JSON fields installed, conflicts, missing, outdated and interrupted instead of native plugin state.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.