bug-detective
Investigates software failures, exceptions, and errors by tracing execution, reproducing the problem, and testing the suspected cause.
Skill by Vepricov
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/vepricov-bug-detective
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Python package
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/bug-detective
What's inside
- Skill name
bug-detective- Description
- Investigates software failures, exceptions, and errors by tracing execution, reproducing the problem, and testing the suspected cause. Use when the user reports a crash, a traceback, an unexpected result, says 'this code throws an error', 'why does this fail', or asks to debug a failing function.
- License
- MIT
- Instructions
- 303 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
Files (9)
- SKILL.md
- debugging-workflow.py · examples/
- debugging-workflow.sh · examples/
- error-handling-patterns.py · examples/
- common-patterns.md · references/
- debugging-tools.md · references/
- javascript-errors.md · references/
- python-errors.md · references/
- shell-errors.md · references/
SKILL.md (first lines)
# Bug Detective A systematic debugging workflow for investigating and resolving code errors, exceptions, and failures. Provides structured debugging methods and common error pattern recognition. ## Core Philosophy Debugging is a scientific problem-solving process that requires: 1. **Understand the problem** - Clearly define symptoms and expected behavior 2. **Gather evidence** - Collect error messages, logs, stack traces 3. **Form hypotheses** - Infer possible causes based on evidence 4. **Verify hypotheses** - Confirm or eliminate causes through experiments 5. **Resolve the issue** - Apply fixes and verify ## Debugging Workflow ### Step 1: Understand the Problem Before starting to debug, clarify the following information: **Required information to collect:** - Complete error message content - Exact location of the error (filename and line number) - Reproduction steps (how to trigger the error) - Expected behavior vs actual behavior - Environment info (OS, versions, dependencies) **Question template:** ``` 1. What is the exact error message? 2. Which file and line does the error occur at? 3. How can this issue be reproduced? Provide detailed steps. 4. What was the expected result? What actually happened? 5. What recent changes might have introduced this issue? ``` ### Step 2: Analyze Error Type Choose a debugging strategy based on error type: | Error Type | Characteristics | Debugging Method | |-----------|----------------|-----------------| | **Syntax Error** | Code cannot be parsed | Check syntax, bracket matching, quotes | | **Import Error** | ModuleNotFoundError | Check module installation, path config | | **Type Error** | TypeError | Check data types, type conversions | | **Attribute Error** | AttributeError | Check if object attribute exists | | **Key Error** | KeyError | Check if dictionary key exists | | **Index Error** | IndexError | Check list/array index range | | **Null Reference** | NoneType/NullPointerException | Check if variable is None | | **Network Error** | ConnectionError/Timeout | Check network connection, URL, timeout settings | | **Permission Error** | PermissionError | Check file permissions, user permissions | | **Resource Error** | FileNotFoundError | Check if file path exists | ### Step 3: Locate the Problem Source Use the following methods to locate the issue: **1. Binary Search Method** - Comment out half the code, check if the problem persists - Progressively narrow the scope until the problematic code is found **2. Log Tracing** - Add print/logging statements at key locations - Track variable value changes - Confirm code execution path **3. Breakpoint Debugging** - Use debugger breakpoint functionality - Step through code execution - Inspect variable state **4. Stack Trace Analysis** - Find the call chain from the stack trace in the error message - Determine the direct cause of the error - Trace back to the root cause ### Step 4: Form and Verify Hypotheses **Hypothesis framework:** ``` Hypothesis: [problem description] causes [error phenomenon] Verification steps: 1. [verification method 1] 2. [verification method 2] Expected results: - If hypothesis is correct: [expected phenomenon] - If hypothesis is wrong: [expected phenomenon] ``` ### Step 5: Apply Fix After fixing, verify: 1. The original error is resolved 2. No new errors have been introduced 3. Related functionality still works correctly 4. Tests added to prevent regression ## Python Common Error Patterns ### 1. Indentation Errors ### 2. Mutable Default Arguments ### 3. Closure Issues in Loops ### 4. Modifying a List While Iterating ### 5. Using `is` for String Comparison ### 6. Forgetting to Call `super().__init__()` ## JavaScript/TypeScript Common Error Patterns ### 1. `this` Binding Issues ### 2. Async Error Handling ### 3. Object Reference Comparison ## Bash/Zsh Common Error Patterns ### 1. Spacing Issues ```bash # ❌ No spaces allowed in assignment
From Vepricov/claude-brainlab, MIT.
More from Vepricov/claude-brainlab
- 0.657score
operon-obsidian-setup
Vepricov
Installs or repairs the laboratory's Operon task boards and project views in an Obsidian vault.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
obsidian-project-bootstrap
Vepricov
Creates or repairs the Obsidian knowledge base and folder mappings for an existing research repository.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
obsidian-project-memory
Vepricov
Maintains canonical project context and durable research decisions in the mapped Obsidian knowledge base.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
obsidian-bases
Vepricov
Creates and edits Obsidian Bases (.base) files with filters, formulas, views, and summaries in valid YAML.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
obsidian-literature-workflow
Vepricov
Develops project-linked reading notes and literature synthesis from papers stored in the Obsidian knowledge base or Zotero.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
obsidian-markdown
Vepricov
Writes and edits Obsidian Flavored Markdown with valid wikilinks, embeds, properties, callouts, comments, and tables.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
json-canvas
Vepricov
Creates and edits Obsidian Canvas (.canvas) files with nodes, edges, groups, and layout following JSON Canvas Spec 1.0.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
git-workflow
Vepricov
Prepares commits, branches and pull requests following the repository's existing Git conventions, including Conventional Commits messages and merge strategy.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
diagnose
Vepricov
Diagnoses hard bugs and performance regressions by building a reproducible feedback loop and testing competing causal hypotheses.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
kaggle-learner
Vepricov
Extracts reusable ML techniques, code patterns, and feature engineering ideas from Kaggle competition winning solutions and maps where they apply.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
doc-coauthoring
Vepricov
Co-authors a technical document, proposal, or specification through context gathering, targeted drafting, and reader-testing review.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
paper-to-social
Vepricov
Creates Telegram, X, or Habr posts from a research paper using verified figures and the user's writing style.
SkillAFreshness: A★ 33Claude Code +9
Signals
- Stars
- 33
- Forks
- 5
- Open issues
- 1
- Last commit (this folder)
- Oct 5, 2026 (23 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/Vepricov/claude-brainlab
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from Vepricov
- 0.657score
kaggle-learner
Vepricov
Extracts reusable ML techniques, code patterns, and feature engineering ideas from Kaggle competition winning solutions and maps where they apply.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
json-canvas
Vepricov
Creates and edits Obsidian Canvas (.canvas) files with nodes, edges, groups, and layout following JSON Canvas Spec 1.0.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
diagnose
Vepricov
Diagnoses hard bugs and performance regressions by building a reproducible feedback loop and testing competing causal hypotheses.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
doc-coauthoring
Vepricov
Co-authors a technical document, proposal, or specification through context gathering, targeted drafting, and reader-testing review.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
git-workflow
Vepricov
Prepares commits, branches and pull requests following the repository's existing Git conventions, including Conventional Commits messages and merge strategy.
SkillAFreshness: A★ 33Claude Code +9 - 0.657score
obsidian-bases
Vepricov
Creates and edits Obsidian Bases (.base) files with filters, formulas, views, and summaries in valid YAML.
SkillAFreshness: A★ 33Claude Code +9
Cite this page
bug-detective skill. Agent Mart. https://agentmart.dev/skills/vepricov-bug-detective (last updated 2026-10-24)