Skip to content
RT-Themes CLI

Offline Project Checks

The current doctor is an offline, read-only metadata inspector. After installing and verifying the CLI:

Terminal window
npx @rtthemes/cli@latest doctor --project /path/to/customer-project

For structured output:

Terminal window
npx @rtthemes/cli@latest doctor --project /path/to/customer-project --json

Doctor does not require a Dashboard approval or contact Club. The npx launcher can contact npm to obtain the CLI; the doctor operation itself checks your project offline.

The inspector reads the local .rtthemes/kit.json and checks its reference digest, core/release identity, vendor dependency, npm lock version/path/integrity, artifact hashes/size, Node requirements and locked peers.

Treat results as local consistency checks. Matching hashes do not by themselves authenticate a publisher. A local-delivery kit retains its review status and warning even if all its bytes match.

Config behavior, routes, CSS, fonts, SEO, builds and CMS semantics are reported as not checked. A successful metadata check does not mean the website is ready to launch.

Doctor does not import Astro config, scan content bodies, read .env/.npmrc, fix files or run your build. Online release checks and automatic fixes are not available in this implementation. Run your product’s own commands separately:

Terminal window
npm run check
npm run build

Use the exact archive, dependency, lock and kit supplied for the same release. Do not hand-edit digest/version fields to suppress a warning. Restore a known matching backup or obtain the correct release metadata. Unknown schema/reference or core mismatches should be resolved before generating a CMS brief.

For theme-specific content and component problems, see NaturaLife Astro troubleshooting. For an interrupted CLI transaction, use update recovery.