Diagnosing Bugs

Diagnosing Bugs is a Quality skill for Claude Code, published by stevesolun in ctx.

578 stars71 forkson stevesolun/ctxAdded 2026/08/25+1% in starsRepository updated 2026/08/24

agentsai-agentsanthropicautomationclaudeclaude-codecontext-managementdeveloper-toolsharnessknowledge-graphllmllm-wikimcpmicro-skillsobsidianreal-timerecommendation-engineskill-managementskillswiki

Install in seconds

Install Diagnosing Bugs

Copy Diagnosing Bugs 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/stevesolun/ctx/tree/main/.agents/skills/diagnosing-bugs ~/.claude/skills/diagnosing-bugs

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/stevesolun/ctx.git

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

In this catalog

Source file: .agents/skills/diagnosing-bugs/SKILL.md in stevesolun/ctx
Installs to: ~/.claude/skills/diagnosing-bugs
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1354 skills

What Diagnosing Bugs does

Diagnosing Bugs uses reproducible evidence, focused hypotheses, and targeted instrumentation to isolate hard bugs and performance regressions. Use it when something is broken, intermittent, or unexpectedly slow.

Diagnosing Bugs is cataloged under Quality on DirSkills. Diagnosing Bugs comes from a repository tagged agents, ai-agents, anthropic, automation and claude.

Documentation

README

Excerpt

Diagnosing Bugs

Start from evidence and adapt the depth of the investigation to the problem. Read relevant repository context and architectural decisions when they exist.

Establish a useful signal

Reproduce the reported symptom with the cheapest signal that distinguishes broken from fixed. A focused test or script is ideal when practical; logs, traces, snapshots, comparisons, or measured timings may be better for other failures. Tighten the loop by improving speed, specificity, and determinism.

If an exact reproduction is unavailable, continue with the strongest evidence available and state the limitation. Request an artifact, access, or temporary instrumentation only when it would materially improve the diagnosis.

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

Frequently asked about Diagnosing Bugs

What else does stevesolun publish alongside Diagnosing Bugs?
Diagnosing Bugs is one of 25 skills that DirSkills catalogs from stevesolun/ctx, the repository it ships in. Its siblings there include Ask Matt, Code Review and Codebase Design. Each one is a separate skill with its own page in this directory, installs the same way Diagnosing Bugs does, and is maintained by stevesolun in that same repository. The rest of the collection is listed on the stevesolun/ctx page.
How does Diagnosing Bugs compare to other Quality skills?
Diagnosing Bugs ranks #1150 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 Diagnosing Bugs against them. Open each page to compare what they document and how they install.