Agent skill

Debug Ohmycode

by AlphaLab-USTC in AlphaLab-USTC/OhMyCode

Guide for debugging OhMyCode issues. An agent skill from AlphaLab-USTC/OhMyCode.

MITAuto-check passedDevelopment

Install Debug Ohmycode

skills CLI

$ npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install AlphaLab-USTC/OhMyCode debug-ohmycode --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debug-ohmycode .claude/skills/debug-ohmycode && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "debug-ohmycode" agent skill from https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode into .claude/skills/debug-ohmycode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-ohmycode", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install AlphaLab-USTC/OhMyCode debug-ohmycode --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/debug-ohmycode .agents/skills/debug-ohmycode && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "debug-ohmycode" agent skill from https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode into .agents/skills/debug-ohmycode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-ohmycode", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install AlphaLab-USTC/OhMyCode debug-ohmycode --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/debug-ohmycode .cursor/skills/debug-ohmycode && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "debug-ohmycode" agent skill from https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode into .cursor/skills/debug-ohmycode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-ohmycode", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/AlphaLab-USTC/OhMyCode.git --path .agents/skills/debug-ohmycode

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install AlphaLab-USTC/OhMyCode debug-ohmycode --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/debug-ohmycode .gemini/skills/debug-ohmycode && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "debug-ohmycode" agent skill from https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode into .gemini/skills/debug-ohmycode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-ohmycode", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install AlphaLab-USTC/OhMyCode debug-ohmycode

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/debug-ohmycode .github/skills/debug-ohmycode && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "debug-ohmycode" agent skill from https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode into .github/skills/debug-ohmycode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-ohmycode", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install AlphaLab-USTC/OhMyCode debug-ohmycode --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/debug-ohmycode .opencode/skills/debug-ohmycode && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "debug-ohmycode" agent skill from https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.agents/skills/debug-ohmycode into .opencode/skills/debug-ohmycode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-ohmycode", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: debug-ohmycode
GitHub stars: 131
Token cost: ~1.3k tokens
SKILL.md length: 434 words
Files: 1
Skills in repo: 10
Repo updated: Apr 2, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Guide for debugging OhMyCode issues. An agent skill from AlphaLab-USTC/OhMyCode.

Works in 4 steps: Check installation: pip3 show ohmycode → Check PATH: which ohmycode && ohmycode… → Reinstall: cd && ./scripts/setup-cli.sh → …
User reports errors
SKILL.md covers When to Use, Diagnostic Flowchart, Category 1: Installation Issues and Category 2: Provider / API…, plus 5 more sections
Calls python3 and pip3

What it does

Debug Ohmycode is an agent skill from AlphaLab-USTC/OhMyCode. Guide for debugging OhMyCode issues. Use when user reports errors, unexpected behavior, or connection problems.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging and LLM cost and token optimization. It works with Microsoft Azure. The repository describes itself as: Minimal and Customizable CC-Style Coding Agent. The licence is MIT.

When your agent uses it

User reports errors
Unexpected behavior
Connection problems

Example prompts

“/debug-ohmycode”

Requirements

Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Check installation: pip3 show ohmycode
Check PATH: which ohmycode && ohmycode --help
Reinstall: cd && ./scripts/setup-cli.sh
Check Python version: python3 --version (needs 3.9+)

What it can do on your machine

Read from SKILL.md and the folder at commit 4d1bb28. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python3
- pip3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pip3, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Debug Ohmycode loads about 1.3k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 434 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~32
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AlphaLab-USTC/OhMyCode at commit 4d1bb28, republished under its MIT licence (© AlphaLab-USTC). 434 words, ~1,280 tokens.

Download SKILL.mdSave it as .claude/skills/debug-ohmycode/SKILL.md (or your agent's skills folder).

name: debug-ohmycode
description: Guide for debugging OhMyCode issues. Use when user reports errors, unexpected behavior, or connection problems.

Debug OhMyCode

Systematic approach to diagnosing and fixing OhMyCode issues.

When to Use

User reports an error or crash
Tool calls fail unexpectedly
API connection issues
Streaming not working
Context compression misbehaving
Memory or conversation persistence issues

Diagnostic Flowchart

Error? → Which category?
├── "command not found" → Installation Issue
├── API/connection error → Provider Issue
├── Tool execution error → Tool Issue
├── "context compression failed" → Context Issue
├── Memory/resume not working → Storage Issue
└── Unexpected AI behavior → Prompt Issue

Category 1: Installation Issues

Symptoms: ohmycode: command not found, ModuleNotFoundError

Steps:

Check installation: pip3 show ohmycode
Check PATH: which ohmycode && ohmycode --help
Reinstall: cd <project_dir> && ./scripts/setup-cli.sh
Check Python version: python3 --version (needs 3.9+)

Category 2: Provider / API Issues

Symptoms: APIError, AuthenticationError, timeout, empty responses

Steps:

Test API connectivity directly:

python

from openai import OpenAI
client = OpenAI(api_key="...", base_url="...")
r = client.chat.completions.create(
    model="...", messages=[{"role": "user", "content": "hi"}], max_tokens=10
)
print(r.choices[0].message.content)

Check config: cat ~/.ohmycode/config.json
- Is api_key set?
- Is base_url correct (trailing /v1)?
- Is model name correct for this provider?
Check provider registration:

python

from ohmycode.providers.base import PROVIDER_REGISTRY, auto_import_providers
auto_import_providers()
print(list(PROVIDER_REGISTRY.keys()))

Check for rate limiting: look for 429 errors in output. OpenAI provider retries 3 times with [1, 2, 5]s delays.
Azure-specific: verify azure_endpoint and azure_api_version in config.

Category 3: Tool Issues

Symptoms: Tool returns error, wrong output, tool not found

Steps:

Check tool is registered:

python

from ohmycode.tools.base import TOOL_REGISTRY, auto_import_tools
auto_import_tools()
print(list(TOOL_REGISTRY.keys()))

Test tool directly:

python

import asyncio
from ohmycode.tools.base import ToolContext
from ohmycode.tools.<name> import <ToolClass>

ctx = ToolContext(mode="auto", agent_depth=0, cwd=".", is_sub_agent=False)
tool = <ToolClass>()
result = asyncio.run(tool.execute({"param": "value"}, ctx))
print(result.output, result.is_error)

Check permissions: if mode=default, dangerous tools need confirmation. Try --mode auto.
Check concurrent_safe flag: if a tool has side effects but is marked concurrent_safe=True, it may have race conditions when called in parallel.

Category 4: Context / Compression Issues

Symptoms: "Circuit breaker open", conversations getting cut off, AI forgetting context

Steps:

Check token budget in config: token_budget and output_tokens_reserved
Check compression thresholds: ohmycode/core/context.py → maybe_compress()
- 75% → snip, 80% → micro_compact, 85% → collapse, 90% → auto_compact
Circuit breaker trips after 3 compression failures — usually means the LLM API is down
For tiktoken accuracy issues: counts are approximate (5-15% off for non-OpenAI models)

Quick fix: Increase token_budget in config, or start a new conversation.

Show full SKILL.md (151 more words)Show less

Category 5: Storage Issues

Symptoms: --resume not working, memories not saving, conversations lost

Steps:

Check directories exist:

bash

ls -la ~/.ohmycode/conversations/
ls -la ~/.ohmycode/memory/

Check conversation files: cat ~/.ohmycode/conversations/<latest>.json | python3 -m json.tool | head
Memory index: cat ~/.ohmycode/memory/MEMORY.md
Resume matching: --resume with no argument loads the most recent file by modification time. With an argument, it matches filename substring.

Category 6: Prompt / Behavior Issues

Symptoms: AI ignores instructions, wrong persona, missing tools in responses

Steps:

Check what system prompt is built:

python

from ohmycode.core.system_prompt import build_system_prompt, find_project_instructions
from ohmycode.tools.base import auto_import_tools
auto_import_tools()
prompt = build_system_prompt(mode="auto", cwd=".")
print(prompt)

Check if OHMYCODE.md / CLAUDE.md is being found:

python

from ohmycode.core.system_prompt import find_project_instructions
print(find_project_instructions("."))

Check memory content: cat ~/.ohmycode/memory/MEMORY.md
Check system_prompt_append in config

General Debugging Tips

Add --mode auto to skip permission prompts during debugging
Keep CLI-first workflow: run with ohmycode only
Check python3 -m pytest tests/ -v to verify nothing is broken
Read the error traceback bottom-up: the last frame is usually the cause
For async issues: look for "RuntimeError: Event loop" — usually means mixing sync/async

Files

Just SKILL.md in .agents/skills/debug-ohmycode of AlphaLab-USTC/OhMyCode.

Open the folder on GitHubat commit 4d1bb28

Compare with similar skills

Debug Ohmycode next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Debug Ohmycode compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Debug Ohmycode this skillAlphaLab-USTC/OhMyCode	131	—	~1.3k	Automated safety check: Pass	MIT	6 mo ago
Aspiremicrosoft/aspire.dev	196	4 repos	~1.1k	Automated safety check: Pass	MIT	yesterday
Adding A Provider API Featurepydantic/pydantic-ai	20k	—	~3.2k	Automated safety check: Pass	MIT	today
Dspy Debugging ObservabilityOmidZamani/dspy-skills	124	1 repos	~2.1k	Automated safety check: Warn	MIT	3 mo ago
Token-Saver Configurationppgranger/token-saver	153	—	~1k	Automated safety check: Pass	Apache-2.0	18 days ago
Langfuse and LLM Gateway LogsKonghaYao/peri	223	—	~4.3k	Automated safety check: Notes	Apache-2.0	yesterday

Similar skills

Aspire
microsoft/aspire.dev
Official
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
196 GitHub starsUsed in 4 repos~1.1k tokens
DevOps & CloudAuto-check passed
Adding A Provider API Feature
pydantic/pydantic-ai
Official
Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI.
20k GitHub stars~3.2k tokensUpdated today
AI & LLM EngineeringAuto-check passed
Dspy Debugging Observability
OmidZamani/dspy-skills
A skill your agent uses for debugging DSPy programs, inspecthistory, tracing LLM calls, custom callbacks, observability, monitoring, and cost tracking.
124 GitHub starsUsed in 1 repo~2.1k tokens
DevOps & CloudAuto-check: warnings
Token-Saver Configuration
ppgranger/token-saver
Checks and tunes token-saver output compression: reads stats, explains why a command was or was not compressed, and edits config files or environment variables.
153 GitHub stars~1k tokensUpdated 18 days ago
Agent WorkflowsAuto-check passed
Langfuse and LLM Gateway Logs
KonghaYao/peri
Queries Langfuse traces, prompts, datasets and sessions, and analyzes local LLM gateway logs for requests, context growth, token use and cache hits.
223 GitHub stars~4.3k tokensUpdated yesterday
AI & LLM EngineeringAuto-check: notes
Debug E2E Pipeline
kubernetes-sigs/cloud-provider-azure
Official
Fetch and analyze Prow e2e pipeline failures for cloud-provider-azure.
294 GitHub stars~3.4k tokensUpdated today
Testing & QAAuto-check passed

Questions about Debug Ohmycode

What does Debug Ohmycode do?

Guide for debugging OhMyCode issues. An agent skill from AlphaLab-USTC/OhMyCode. Debug Ohmycode is an agent skill from AlphaLab-USTC/OhMyCode. Guide for debugging OhMyCode issues.

When should I use Debug Ohmycode?

Debug Ohmycode fits situations like: user reports errors; unexpected behavior; connection problems.

How do I install Debug Ohmycode in Claude Code?

Run `npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a claude-code`. Or copy the skill folder (.agents/skills/debug-ohmycode in AlphaLab-USTC/OhMyCode) into .claude/skills/debug-ohmycode in your project. Claude Code loads it when a task matches its description.

How do I install Debug Ohmycode in Codex?

Run `npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a codex`. Or copy the skill folder (.agents/skills/debug-ohmycode in AlphaLab-USTC/OhMyCode) into .agents/skills/debug-ohmycode in your project. Codex loads it when a task matches its description.

Can I use Debug Ohmycode in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AlphaLab-USTC/OhMyCode --skill debug-ohmycode -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-ohmycode, .gemini/skills/debug-ohmycode, .github/skills/debug-ohmycode and .opencode/skills/debug-ohmycode in your project.

What does Debug Ohmycode need to run?

Going by SKILL.md and its folder, Debug Ohmycode needs the command-line tools its instructions call (python3 and pip3). Our summary lists: Python 3.

Does Debug Ohmycode access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Debug Ohmycode safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Debug Ohmycode use?

Debug Ohmycode is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug Ohmycode use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Debug Ohmycode?

Skills that share tags, products or a category with Debug Ohmycode: Aspire (microsoft/aspire.dev, 196 stars), Adding A Provider API Feature (pydantic/pydantic-ai, 20k stars), Dspy Debugging Observability (OmidZamani/dspy-skills, 124 stars) and Token-Saver Configuration (ppgranger/token-saver, 153 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug Ohmycode?

AlphaLab-USTC (a GitHub user) maintains it in AlphaLab-USTC/OhMyCode, which has 131 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on April 2, 2026.

Source: AlphaLab-USTC/OhMyCode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Debug Ohmycode

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Debug OhMyCode

When to Use

Diagnostic Flowchart

Category 1: Installation Issues

Category 2: Provider / API Issues

Category 3: Tool Issues

Category 4: Context / Compression Issues

Category 5: Storage Issues

Category 6: Prompt / Behavior Issues

General Debugging Tips

Files

Compare with similar skills

Similar skills

More from AlphaLab-USTC/OhMyCode

Related

Questions about Debug Ohmycode