doctor

To diagnose oh-my-droid installation issues, scan settings.json hooks, ~/.factory/hooks scripts, and caches to detect deprecated bash scripts and stale resources. The diagnostic process compares installed plugin versions against npm, verifies FACTORY.md markers, and flags extraneous curl-installed agents.

Factory Droid fails to start after an upgrade when leftover legacy hooks or cached plugin versions obstruct the new workflow. Scanning settings.json for deprecated bash scripts and pruning stale caches resolves these startup failures by ensuring only known-good resources are loaded.

The best way to fix stale oh-my-droid plugin caches is to run a diagnostic audit that compares installed versions to npm, counts cached resources, and verifies FACTORY.md markers. This generates a structured report outlining fixes like pruning caches and refreshing configuration files.

Yes, you can use automated diagnostics to remove legacy curl-installed Factory Droid agents. The diagnostic scan identifies extraneous cached and curl-installed agents, commands, and skills, then invites user confirmation before outlining fixes to prevent duplication and conflicts.

You need to check oh-my-droid plugin health and settings.json hooks when Factory Droid installations behave unexpectedly or fail to start. Running diagnostics after upgrades ensures no deprecated bash scripts or outdated plugins conflict with the latest release.

Yes, the doctor skill detects missing FACTORY.md markers and outdated oh-my-droid plugins by verifying installed versus latest npm versions. It audits supporting configuration files, identifies missing or outdated FACTORY.md content, and recommends refreshing the markers to maintain functional requirements.