doctor

Diagnose oh-my-copilot installation issues and apply safe repairs.

10|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill doctor-lee-sihyeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/Lee-SiHyeon/oh-my-copilot/tree/main/.github/skills/doctor
Command: npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill doctor-lee-sihyeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The doctor skill helps users quickly identify and resolve common oh-my-copilot installation failures such as missing dependencies, broken symlinks, invalid hooks.json, and incorrect script permissions.

Core Features & Use Cases

  • Installation path diagnosis: Detects the active oh-my-copilot plugin directory across supported Copilot CLI install locations.
  • Integrity checks: Finds broken symlinks, validates hooks.json as parseable JSON, and verifies script executability for scripts/*.sh.
  • Environment readiness: Checks for required command-line dependencies (sqlite3, jq, git) and reports the installed plugin version when available.
  • Safe guided repair: Removes broken symlinks and fixes script permissions when issues are found, while providing non-destructive guidance for missing dependencies and JSON problems.

Quick Start

Tell an AI agent to run the doctor skill to perform an oh-my-copilot installation health check and apply safe fixes after reporting issues.

Frequently Asked Questions about doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose oh-my-copilot installation issues when hooks fail to run?

Diagnose oh-my-copilot installation issues by validating plugin directory integrity, checking hooks.json correctness with jq, and verifying script execution permissions to identify why hooks fail to run.

Why does my Copilot CLI setup report missing tools or broken symlinks?

Copilot CLI setups report missing tools or broken symlinks when required command-line dependencies like sqlite3, jq, and git are absent, or when plugin directory symlinks sustain damage preventing agents and tests from working.

What is the best way to repair a malformed hooks.json file in Copilot CLI?

The best way to repair a malformed hooks.json file is to validate its JSON structure using jq, detect parseable JSON errors, and apply non-destructive guidance to correct the formatting problems.

Can I safely fix script execution permissions for oh-my-copilot plugins without breaking the setup?

You can safely fix script execution permissions by applying guarded repairs like chmod +x to scripts/*.sh files, ensuring the oh-my-copilot plugin setup remains intact while restoring executability.

How do I check if sqlite3, jq, and git are available for my Copilot CLI environment readiness?

Check environment readiness for sqlite3, jq, and git command availability by scanning the plugin root, reporting the installed plugin version, and verifying all required command-line dependencies are present.

Do I need to manually remove broken symlinks preventing my Copilot CLI agents from working?

You do not need to manually remove broken symlinks preventing Copilot CLI agents from working; the doctor skill applies guarded fixes using rm -f to safely remove confirmed broken symlinks automatically.