omc-doctor

Diagnose Copilot installation issues by running the doctor skill to verify plugin installation, detect legacy hooks, validate the COPILOT_CONFIG_DIR path, and check settings.json. It provides guided remediation steps to repair local configurations safely.

Copilot plugin configuration problems after updates are often caused by legacy hooks, outdated copilot-instructions, or cache corruption. Run diagnostics to detect version mismatches and deprecated scripts, then follow safe remediation steps to remove outdated content and clear caches.

Validate COPILOT_CONFIG_DIR paths and settings.json presence by running a health check that reads and interprets your local configuration structure. This verifies plugin cache integrity and ensures the Copilot plugin runs with the correct settings.

The best way to remove legacy hooks and outdated Copilot-instructions is through guided remediation that identifies deprecated files and scripts, performs safe cache clearance, removes obsolete content, and applies updated setup instructions for local environments.

Yes, you can fix oh-my-copilot plugin version mismatches on a local setup by running diagnostics that detect version discrepancies and validate plugin cache integrity, followed by applying safe remediation steps including cache cleanup and guided setup updates.

When Copilot troubleshooting detects deprecated scripts but the plugin still fails, perform a full cache clearance, remove all identified legacy hooks and outdated instructions, then rerun the health check to validate that settings.json and COPILOT_CONFIG_DIR paths are correctly configured.