Diagnosing Bugs

Find the cause of a hard bug, outage or slowdown by building a red-capable feedback loop before forming any theory. Use when something is broken, failing, flaky, slow or keeps recurring, including machine-level problems such as lost logins, restarts or a gate that fails open.

48 stars 6 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add frankxai/claude-skills-library

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add frankxai/claude-skills-library --skill diagnosing-bugs
Manual install
git clone --depth 1 https://github.com/frankxai/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/absorbed/engineering/diagnosing-bugs ~/.claude/skills/diagnosing-bugs

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Diagnosing bugs

The whole skill is one discipline: get a command that goes red on this exact bug before you reason about causes. With that command, bisecting, testing hypotheses and verifying the fix are mechanical. Without it, reading code produces confident wrong answers, and the estate has a long record of gates that "worked" until someone tested them.

## Redact first

Commands, logs and captured requests carry tokens and account names. Replace secrets with `<REDACTED>`, keep credentials in environment variables or Infisical, and quote only the lines that carry the signal. The secret guard will block a tool call that leaks one; do not route around it.

## 1. Build the loop (spend most of the effort here)

Pick the first that reaches the bug:

1. A failing test at the seam that hits it (`pnpm test -- <name>`, `uv run pytest -k <name>`, `node --test <file>`).
2. A `curl` or HTTP script against a running dev server or a preview URL.
3. A CLI run on a fixture, diffed against a known-good output.
4. A headless browser script through the shared `browse` Chromium or BrowserOS, asserting on DOM, console or network.
5. A replayed capture: save the real request, event or payload to disk and push it through the code path alone.
6. A minimal harness: one service, mocked dependencies, one call.
7. A property or fuzz loop for "sometimes wrong".
8. A bisection script for "worked at X, broken at Y" (`git bisect run <script>`).
Read the full skill on GitHub

Details

Skill name
diagnosing-bugs
Path
absorbed/engineering/diagnosing-bugs/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Diagnosing Bugs skill do?

Find the cause of a hard bug, outage or slowdown by building a red-capable feedback loop before forming any theory. Use when something is broken, failing, flaky, slow or keeps recurring, including machine-level problems such as lost logins, restarts or a gate that fails open.

How do I install the Diagnosing Bugs skill?

Claude Code plugin: /plugin marketplace add frankxai/claude-skills-library. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Diagnosing Bugs popular?

It lives in frankxai/claude-skills-library, which has 48 GitHub stars and 6 forks.

Related skills

Acos Meta

48

frankxai/claude-skills-library

ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.

Software Development

Acos Visual Gen

48

frankxai/claude-skills-library

Generate research-grounded visuals using the InfoGenius pipeline. Use when creating infographics, diagrams, educational visuals, or any image that benefits from factual accuracy. Supports 8 visual styles (3D, technical, minimalist, photorealistic, futuristic, vintage, cartoon, standard) and 4 audience levels.

Images, Video & Audio

Agent Harness Construction

48

frankxai/claude-skills-library

Shape an agent's tools, observations, and recovery without adding a second coordinator. Use when defining a tool, a skill, a hook, or a worktree lane.

AI, LLMs & Agents

Greek Philosopher

48

frankxai/claude-skills-library

Channel ancient wisdom through Socratic questioning, Stoic principles, and philosophical inquiry to examine life's deepest questions with poetic eloquence and timeless insight. Use when examining a life decision, seeking Stoic perspective on adversity, or wanting Socratic questioning of an assumption.

Other

Ceo Review

43

0xranx/agentbrief

When reviewing product decisions, feature scope, or user-facing changes from a founder/CEO perspective. Use when the user says 'does this make sense,' 'should we build this,' 'review the product,' 'is this good enough,' 'founder review,' 'product sense check,' or before any significant launch. This is the strategic taste layer — not engineering quality, but product quality.

Other

Si

48

frankxai/claude-skills-library

Superintelligence router — composes /superintelligence reasoning with swarm execution only when verb intent demands it. Defaults to reasoning-only to prevent runaway swarm cost. Triggers — /si <ask>, "think deeply about X", "analyze X with full depth", or any ask requiring multi-perspective + first-principles + contrarian framing.

Other

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.