debug-ohmycode

Diagnose OhMyCode installation, provider, tool, and storage failures.

131|4|Updated Apr 1, 2026

Search Tags:#debugging #troubleshooting #api #cli #tooling #ohmycode

Ready to run

npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill debug-ohmycode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-ohmycode
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill debug-ohmycode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps troubleshoot OhMyCode when it fails to install, cannot connect to a provider, misbehaves during tool execution, or loses memory and resume state.

Core Features & Use Cases

Installation debugging: Resolve command-not-found, PATH, and Python version issues.
Provider and API troubleshooting: Diagnose authentication, timeout, base URL, Azure, and rate-limit problems.
Tool and runtime diagnosis: Check tool registration, permissions, context compression, storage, and prompt behavior.
Use Case: A user reports that OhMyCode streams nothing and resume does not work; this Skill guides a structured investigation from environment setup through storage verification.

Quick Start

Use the debug-ohmycode skill to diagnose why OhMyCode is not starting, connecting, or behaving correctly.

Frequently Asked Questions about debug-ohmycode

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

FAQPage Schema

How do I fix OhMyCode command-not-found errors after installation?▼

Fixing OhMyCode command-not-found installation errors requires inspecting your PATH configuration and Python version to resolve environment setup issues. This Skill guides structured investigation through CLI behavior and registries to isolate the root cause and recommend a fix.

Why does my CLI tool fail to connect to the API provider?▼

CLI tool API connection failures often stem from authentication, timeout, base URL, or rate-limit problems. This Skill diagnoses provider configurations by inspecting logs and CLI behavior to isolate connection issues and recommend appropriate fixes.

What is the best way to troubleshoot broken tool execution and context compression issues?▼

Troubleshooting broken tool execution and context compression issues involves checking tool registration, permissions, and storage behavior. This Skill inspects configuration and prompt behavior to isolate runtime failures and recommend corrective actions.

How do I recover missing resume state and memory in OhMyCode?▼

Recovering missing resume state and memory in OhMyCode requires verifying storage configurations and inspecting logs. This Skill guides a structured investigation from environment setup through storage verification to isolate why state is lost.

Does this debugging approach work for Azure provider and rate-limit problems?▼

Yes, this debugging approach works for Azure provider and rate-limit problems by diagnosing authentication and connection configurations. The Skill inspects provider settings and CLI behavior to isolate API-specific failures and recommend fixes.