CLI Doctoring Workflow - diagnostics that move users forward

Use this skill when designing or reviewing a CLI doctor, diagnose, preflight, or health-check command. The command should explain what it checked, what failed, how confident it is, what the user can do next, and what evidence is safe to share in a support request.

The goal is not to prove every part of a system. The goal is to catch common environment and configuration failures early, give precise repair hints, and avoid sending users into vague troubleshooting loops.

Core Standard

A doctor command earns its place when it is: