/doctor

> Diagnose and repair system issues -- dependencies, config, engine health.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/doctor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Diagnose and repair system issues -- dependencies, config, engine health.

Teams using /doctor should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/doctor/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/operations/doctor/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/doctor/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /doctor Compares

Feature / Agent	/doctor	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Diagnose and repair system issues -- dependencies, config, engine health.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /doctor

> Diagnose and repair system issues -- dependencies, config, engine health.

## Usage
```
/doctor [--fix]
```

## What It Does
Checks that all system components are properly configured and operational. Verifies Elixir/Mix installation, engine compilation, SQLite database, folder structure, and MCP server connectivity. Reports issues with specific remediation steps.

## Implementation
1. **Elixir toolchain** -- verify `elixir --version`, `mix --version`.
2. **Engine compilation** -- `cd engine && mix compile` succeeds.
3. **Dependencies** -- `cd engine && mix deps.get` up to date.
4. **Database** -- SQLite file exists and is readable.
5. **Folder structure** -- all 12 numbered folders exist with context.md.
6. **Search index** -- FTS5 index is populated and queryable.
7. **Rhythm files** -- required workflow files exist.
8. **Config** -- engine config is valid.

With `--fix`: attempt to repair issues automatically (install deps, create missing files, rebuild index).

## Examples
```bash
# Check system health
/doctor

# Check and auto-fix issues
/doctor --fix
```

## Command