doctor

What it does

/cl-dev:doctor runs a health check of your CodeLantern setup. It looks over your local configuration and the connections the workflow depends on, then reports what's working and what isn't. When something is off, it tells you what's wrong and points you at the fix, so you can clear the blocker and get back to work instead of guessing.

When to use it

Reach for it whenever your setup feels wrong and you'd rather diagnose than guess:

• Right after /cl-dev:init, to confirm the repository is wired up correctly before you start real work.
• When a skill won't run or behaves unexpectedly (for example, issues or pull requests aren't being found, or the workflow can't tell where your work lives).
• When you switch machines, repositories, or connections and want to be sure everything is still in place.

It's a good first stop any time you're unsure whether the problem is your setup or the task itself.

How to invoke it

In your coding agent, run:

/cl-dev:doctor

No arguments are needed. Run it in the repository you want to check.

For doctor to give you a full picture, you should already have a CodeLantern platform account connected to your repository, GitHub credentials configured in your environment (for example via gh auth login), and the plugin installed. If you haven't done the one-time setup yet, start with Install and /cl-dev:init first.