New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

OMC Session Debugger

by Yeachan-Heo in Yeachan-Heo/oh-my-claudecode

Diagnoses a broken oh-my-claudecode session or repository state from logs, traces, state and a narrow reproduction, then names the smallest next fix.

MITAuto-check passedDevelopment

Install OMC Session Debugger

skills CLI
$ npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a claude-code

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

GitHub CLI
$ gh skill install Yeachan-Heo/oh-my-claudecode debug --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/Yeachan-Heo/oh-my-claudecode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debug .claude/skills/debug && 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/

Facts

Skill name
debug
GitHub stars
40k
Token cost
~361 tokens
SKILL.md length
189 words
Files
1
Skills in repo
47
Repo updated
First seen
Licence
MIT

At a glance

Diagnoses a broken oh-my-claudecode session or repository state from logs, traces, state and a narrow reproduction, then names the smallest next fix.

  • Works in 5 steps: Read the user’s issue description… → Inspect the most relevant local evidence… → Reproduce the issue narrowly if possible. → …
  • An OMC workflow or hook stopped behaving as expected and the cause is unclear
  • SKILL.md covers Goal, Workflow, Rules and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill is for troubleshooting a current OMC or Claude Code session problem, a broken workflow or confusing runtime behavior. The agent reads the issue closely, inspects the most relevant local evidence first (trace tools, state tools, notepad or project memory, failing tests or commands), reproduces the problem narrowly where possible, and separates symptoms from root cause.

Its rules favor real evidence over guesses, using trace and state surfaces when orchestration, hooks or agent flow are involved, and saying plainly when the cause is a product or runtime bug rather than your app code. It avoids broad rewrites before the failure is isolated, tags temporary debug output so cleanup is a single grep, redacts secrets from logs and traces, and points to the refit or architecture-survey skills when a missing seam is the finding. The report lists the observed failure, a root-cause hypothesis, the evidence and the smallest next action.

When your agent uses it

  • An OMC workflow or hook stopped behaving as expected and the cause is unclear
  • A session shows confusing runtime behavior that logs and traces might explain
  • Telling whether a failure comes from your code or from the orchestration runtime

Example prompts

  • “My team workflow stalled halfway through. Check the trace and state and tell me why.”
  • “Debug why the pre-commit hook never fires in this session.”
  • “Find the real failure behind these repeated agent errors and suggest the smallest fix.”

Workflow steps

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

  1. Read the user’s issue description carefully.
  2. Inspect the most relevant local evidence first
  3. Reproduce the issue narrowly if possible.
  4. Distinguish symptoms from root cause.
  5. Recommend the smallest next fix or verification step.

What it can do on your machine

Read from SKILL.md and the folder at commit 454bae0. 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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

OMC Session Debugger loads about 361 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 189 words of instructions outside code blocks.

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

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 Yeachan-Heo/oh-my-claudecode at commit 454bae0, republished under its MIT licence (© Yeachan-Heo). 189 words, ~361 tokens.

Download SKILL.mdSave it as .claude/skills/debug/SKILL.md (or your agent's skills folder).
name
debug
description
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

Debug

Use this skill when the user wants help diagnosing a current OMC/Claude-Code session problem, workflow breakage, or confusing runtime behavior.

Goal

Find the real failure signal quickly and explain the next corrective step.

Workflow

  1. Read the user’s issue description carefully.
  2. Inspect the most relevant local evidence first:
    • trace tools
    • state tools
    • notepad / project memory when relevant
    • failing tests or commands
  3. Reproduce the issue narrowly if possible.
  4. Distinguish symptoms from root cause.
  5. Recommend the smallest next fix or verification step.

Rules

  • Prefer real evidence over guesses.
  • Use the trace/state surfaces when the issue involves orchestration, hooks, or agent flow.
  • If the issue is actually a product/runtime bug rather than app code, say so plainly.
  • Do not prescribe broad rewrites before isolating the failure.
  • Tag temporary debug output [DEBUG-<4hex>]; cleanup is then a single grep.
  • Redact secrets from logs and traces before they leave the session.
  • If the failure traces to a missing or wrong seam, say so as the finding and point at refit or architecture-survey — the environment lesson outlives the fix.

Output

  • Observed failure
  • Root-cause hypothesis
  • Evidence for that hypothesis
  • Smallest next action

© Yeachan-Heo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/debug of Yeachan-Heo/oh-my-claudecode.

Open the folder on GitHubat commit 454bae0

Compare with similar skills

OMC Session Debugger 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.

OMC Session Debugger compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OMC Session Debugger this skillYeachan-Heo/oh-my-claudecode40k—~361Automated safety check: PassMIT
Octocode Code Researchbgauryy/octocode946—~1.5kAutomated safety check: PassMIT
Muse Code Product Doctorasgeirtj/system_prompts_leaks69k—~3.5kAutomated safety check: PassCC0-1.0
Root Cause Investigationgarrytan/gstack136k—~12kAutomated safety check: NotesMIT
Targeted Emergency Bug FixVeryGoodOpenSource/vgv-wingspan108—~1.9kAutomated safety check: PassMIT
Flowstudio Power Automate Debuggithub/awesome-copilot40k2 repos~5kAutomated safety check: PassMIT

Similar skills

  • Octocode Code Research

    bgauryy/octocode

    Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.

    946 GitHub stars~1.5k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Muse Code Product Doctor

    asgeirtj/system_prompts_leaks

    Diagnoses a Muse Code installation's own failures from binary and session evidence, instead of treating the report as an ordinary repository bug.

    69k GitHub stars~3.5k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Root Cause Investigation

    garrytan/gstack

    Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.

    136k GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check: notes

  • Targeted Emergency Bug Fix

    VeryGoodOpenSource/vgv-wingspan

    Applies a minimal fix to an emergency bug through triage, root-cause location, a hotfix branch and a blast-radius check, with tests and review still required.

    108 GitHub stars~1.9k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Flowstudio Power Automate Debug

    github/awesome-copilot

    Official

    Debug failing Power Automate cloud flows using the FlowStudio MCP server.

    40k GitHub starsUsed in 2 repos~5k tokens
    DevelopmentAuto-check passed

  • Vibe Reflect And Compound

    ash1794/vibe-engineering

    Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent…

    162 GitHub stars~864 tokensUpdated today
    DevelopmentAuto-check passed

More from Yeachan-Heo/oh-my-claudecode

All 47 skills in this repo

  • Autopilot

    Yeachan-Heo/oh-my-claudecode

    Takes a short product idea through requirements, design, planning, parallel implementation, QA cycles and multi-reviewer validation to produce working code.

    40k GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check passed

  • Ask Advisor Routing

    Yeachan-Heo/oh-my-claudecode

    Sends a question or task to another locally installed agent CLI, such as Codex or Gemini, through omc ask and saves the answer as a file.

    40k GitHub stars~572 tokensUpdated today
    Auto-check passed

  • Self-Improve Evolutionary Loop

    Yeachan-Heo/oh-my-claudecode

    Runs an autonomous improvement loop on a repository: agents propose and execute plans, a tournament picks the winner by benchmark, and each round is recorded and plotted.

    40k GitHub stars~5.3k tokensUpdated today
    Auto-check: warnings

  • Ask Navigator

    Yeachan-Heo/oh-my-claudecode

    Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.

    40k GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • OMC Mode Cancellation

    Yeachan-Heo/oh-my-claudecode

    Detects and gracefully cancels whichever OMC mode, autopilot, ralph, swarm, pipeline, or team, is currently active, then clears its state.

    40k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Hierarchical AGENTS.md Generator

    Yeachan-Heo/oh-my-claudecode

    Maps a codebase directory by directory and writes linked AGENTS.md files, each pointing to its parent, to document what each area contains.

    40k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Categories

Questions about OMC Session Debugger

What does OMC Session Debugger do?

Diagnoses a broken oh-my-claudecode session or repository state from logs, traces, state and a narrow reproduction, then names the smallest next fix. This skill is for troubleshooting a current OMC or Claude Code session problem, a broken workflow or confusing runtime behavior. The agent reads the issue closely, inspects the most relevant local evidence first (trace tools, state tools, notepad or project memory, failing tests or commands), reproduces the problem narrowly where possible, and separates symptoms from root cause.

When should I use OMC Session Debugger?

OMC Session Debugger fits situations like: an OMC workflow or hook stopped behaving as expected and the cause is unclear; A session shows confusing runtime behavior that logs and traces might explain; telling whether a failure comes from your code or from the orchestration runtime.

How do I install OMC Session Debugger in Claude Code?

Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a claude-code`. Or copy the skill folder (skills/debug in Yeachan-Heo/oh-my-claudecode) into .claude/skills/debug in your project. Claude Code loads it when a task matches its description.

How do I install OMC Session Debugger in Codex?

Run `npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a codex`. Or copy the skill folder (skills/debug in Yeachan-Heo/oh-my-claudecode) into .agents/skills/debug in your project. Codex loads it when a task matches its description.

Can I use OMC Session Debugger 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 Yeachan-Heo/oh-my-claudecode --skill debug -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, .gemini/skills/debug, .github/skills/debug and .opencode/skills/debug in your project.

What does OMC Session Debugger need to run?

SKILL.md names no scripts, command-line tools or credentials: OMC Session Debugger is instructions for the agent only.

Does OMC Session Debugger 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 OMC Session Debugger 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 OMC Session Debugger use?

OMC Session Debugger 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 OMC Session Debugger use?

About 361 tokens (SKILL.md is roughly 1.4k 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 OMC Session Debugger?

Skills that share tags, products or a category with OMC Session Debugger: Octocode Code Research (bgauryy/octocode, 946 stars), Muse Code Product Doctor (asgeirtj/system_prompts_leaks, 69k stars), Root Cause Investigation (garrytan/gstack, 136k stars) and Targeted Emergency Bug Fix (VeryGoodOpenSource/vgv-wingspan, 108 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OMC Session Debugger?

Yeachan-Heo (a GitHub user) maintains it in Yeachan-Heo/oh-my-claudecode, which has 39,638 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 7, 2026.

Source: Yeachan-Heo/oh-my-claudecode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.