Debugging

by code-yeongyu

Debugging is a Quality skill for Claude Code, published by code-yeongyu in lazycodex.

3.2K stars201 forkson code-yeongyu/lazycodexAdded 2026/08/17+1% in starsRepository updated 2026/08/09

View source on GitHub Download repo ZIP

aiai-agentsclaudeclaude-codeclicodexdeveloper-toolslazylazycodexoh-my-openagentomoopenaiorchestrationtypescript

Install in seconds

Install Debugging

Copy Debugging into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/code-yeongyu/lazycodex/tree/main/plugins/omo/skills/debugging ~/.claude/skills/debugging

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/code-yeongyu/lazycodex.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: plugins/omo/skills/debugging/SKILL.md in code-yeongyu/lazycodex
Installs to: ~/.claude/skills/debugging
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Debugging does

Debugging applies a hypothesis-driven workflow to find root causes of crashes, silent failures, wrong responses, memory leaks, and async misbehavior in any language or binary, using runtime evidence and locking fixes with failing tests. Use it when attaching debuggers, reverse engineering binaries, or reproducing flaky or CI-only failures.

Debugging is cataloged under Quality on DirSkills. Debugging comes from a repository tagged ai, ai-agents, claude, claude-code and cli.

Documentation

README

Excerpt

Debugging

You are a hypothesis-driven debugger. Two disciplines apply regardless of language, runtime, or whether you have source:

Runtime truth beats code reading. Every claim about why the bug happens must come from observed state — never from a plausible story spun from reading code.
Leave no trace. Debugging creates artifacts. Every artifact is journaled and removed before you call the task done.

The rest of this file is a map. The knowledge is in references/. This file cannot teach you how to debug — it can only tell you which reference will, for your exact situation.

🚨 READ THE REFERENCES. THIS IS NOT OPTIONAL.

This is the opening of the README. Read the full README on GitHub.

Commands Debugging provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/git-master

Frequently asked about Debugging

What else does code-yeongyu publish alongside Debugging?
Debugging is one of 25 skills that DirSkills catalogs from code-yeongyu/lazycodex, the repository it ships in. Its siblings there include Ast-Grep, Bug Fix Contribution and Codex Rules. Each one is a separate skill with its own page in this directory, installs the same way Debugging does, and is maintained by code-yeongyu in that same repository. The rest of the collection is listed on the code-yeongyu/lazycodex page.
How does Debugging compare to other Quality skills?
Debugging ranks #406 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Debugging against them. Open each page to compare what they document and how they install.