Checkup — Diagnose and Fix Your Machine

Environments break in small, ordinary ways: a command that worked yesterday says "not found", an install half-finished, a new terminal behaves differently. Where workstation, editor, and git set the machine up once, checkup is the skill a beginner runs any time to find what is red and walk the fix — the same on macOS, Windows, and Linux. Nothing it does is destructive: it reads state, reports it plainly, and repairs only what is broken.

Step 0 — Scope check

Read the setup records if they exist — ~/.codehance/machine.md (OS, shell, package manager), ~/.codehance/editor.md, and ~/.codehance/git.md — so a "missing" result is meaningful rather than a guess. Detect the operating system (macOS / Windows / Linux); every repair step comes from the matching reference, so only that one loads. If workstation has never run, say so and send the user there first — checkup verifies and repairs a setup, it does not create one from zero.