Skip to content
cccskills
FreePublished on GitHub

debug

Diagnose problems in OMC or Claude Code sessions using logs, execution traces, saved state, and focused reproduction. Receive a clear account of the failure, a supported cause hypothesis, and the smallest next corrective action.

OriginalShow the original description

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

See how to install

Good for

  • Diagnosing a broken Claude Code workflow
  • Investigating unexpected hook or agent behavior
  • Narrowing down causes of failing tests or commands
  • Choosing the next fix based on local evidence

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.

  • Clarifying instructions in CLAUDE.md
  • Making specifications and tickets actionable
  • Adding completion criteria to skill procedures
Yeachan-Heo/oh-my-claudecode40.1KUpdated Oct 20, 2026

ai-slop-cleaner

FreeSummary

Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.

  • Removing duplicate logic and unused code
  • Simplifying unnecessary wrappers without changing behavior
  • Cleaning up only a specified set of changed files
Yeachan-Heo/oh-my-claudecode40.1KUpdated Oct 20, 2026

Review module relationships and change history to identify structural improvements in a codebase. Receive ranked candidates with file references, suggested changes, and risks, plus a recommendation for where to start, without modifying code.

  • Reviewing architecture after a batch of changes
  • Investigating changes that touch too many files
  • Prioritizing structural improvements
Yeachan-Heo/oh-my-claudecode40.1KUpdated Oct 20, 2026

ask

FreeSummary

Send questions, review requests, or implementation tasks to a supported local AI command-line tool through one shared command. The wrapper handles provider-specific options and saves the result as a Markdown file for later reference.

  • Requesting a security review of a patch
  • Seeking UX suggestions for a user flow
  • Drafting an implementation plan for an issue
Yeachan-Heo/oh-my-claudecode40.1KUpdated Oct 20, 2026

ask-navigator

FreeSummary

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

  • Clarifying the destination of an early idea
  • Mapping decisions and their dependencies
  • Resuming unresolved decisions across sessions
Yeachan-Heo/oh-my-claudecode40.1KUpdated Oct 20, 2026

autopilot

FreeSummary

Turn a short product idea into working code through requirements analysis, technical planning, implementation, testing, and review. It coordinates agents across these stages, fixes detected problems, and reports assumptions that still need a human decision.

  • Building a product from a short idea
  • Creating a bookstore inventory API
  • Developing a habit-tracking command-line tool
Yeachan-Heo/oh-my-claudecode40.1KUpdated Oct 20, 2026

See all skills by Yeachan-Heo

Report a problem with this skill