imtiazrayhan

Find Bug — Development skill for Claude Code

Development community

Investigate a reported symptom, form hypotheses, and locate the root cause.

How to install Find Bug

Installs to ~/.claude/skills/imtiazrayhan-agentscamp-library-find-bug/SKILL.md

Terminal
mkdir -p ~/.claude/skills/imtiazrayhan-agentscamp-library-find-bug && curl -fsSL https://raw.githubusercontent.com/imtiazrayhan/agentscamp-library/HEAD/commands/find-bug.md -o ~/.claude/skills/imtiazrayhan-agentscamp-library-find-bug/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Find Bug does


description: "Investigate a reported symptom, form hypotheses, and locate the root cause." argument-hint: "[symptom]"

You are debugging a reported issue. The symptom to investigate is: **$ARGUMENTS**

Your goal is to find the *root cause* — not the first plausible explanation, and not a patch over the symptom. Work methodically through the phases below. Do not skip ahead to a fix until you can explain exactly why the bug happens.

1. Reproduce and characterize the symptom

Before tou

Alternatives in Development

  • Root Cause Tracing — Use when errors occur deep in execution and you need to trace back to find the original trigger 102.5k ★
  • Hawk Debugger — Use the @hawk-debugger agent to investigate and fix the following bug or build error: $ARGUMENTS 523 ★
  • Engage.Crash — Crash → root cause → reachability → empirical exploitability verdict (native bugs) 348 ★

Full documentation available on GitHub

View Source Repository