skills.rest
brainbrewlabs
brainbrewlabsOFFICIAL
Explore all skills by this author →
GitHub

debugging

Diagnose and fix straightforward bugs and runtime errors in codebases.

7|3|Updated Mar 17, 2026
Search Tags:#debugging#grep#bug-fix#stack-trace#test-failure#code-diagnosis
One-click install
npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill debugging-brainbrewlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/brainbrewlabs/brainbrew-devkit/tree/main/plugin/config/templates/develop/skills/debugging
Command: npx skills add https://github.com/brainbrewlabs/brainbrew-devkit --skill debugging-brainbrewlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Focused, rapid triage and repair for straightforward code errors that have a clear error message or failing test, helping developers get back to green without large refactors.

Core Features & Use Cases

  • Symptom collection: Inspect error messages, stack traces, and the triggering action to identify the exact failure.
  • Source location: Use search and file reads to locate the offending code and relevant recent changes.
  • Minimal fixes & verification: Form a hypothesis, apply a minimal corrective edit, and re-run the failing test or command to confirm resolution.
  • Use Case: Fix an off-by-one error causing a failing unit test, correct a wrong import that throws an immediate import error, or patch a typo that causes a runtime exception.

Quick Start

Diagnose and fix the error "IndexError: list index out of range" in utils.py line 42 and rerun the failing test to confirm resolution.

Frequently Asked Questions about debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a failing unit test with a clear error message?▼

Fix a failing unit test by reading the error text, locating the offending code with grep, applying a minimal corrective edit, and rerunning the failing test command to verify the bug is resolved.

What is the best way to diagnose an off-by-one error or wrong import?▼

Diagnosing an off-by-one error or wrong import requires reading the error text and source files, searching with grep or glob to pinpoint the mistake, and making a minimal edit verified by rerunning the command.

Can I use this to patch a runtime exception caused by a typo?▼

Yes, you can patch a runtime exception caused by a typo by collecting the error symptom, locating the exact source file, applying a minimal corrective edit, and rerunning the triggering action to confirm resolution.

Does this approach work for fixing complex bugs requiring large refactors?▼

No, this approach does not work for complex bugs requiring large refactors, as it is designed for straightforward code errors like missing null checks, wrong imports, and single-error messages with clear failures.

How do I resolve an IndexError list index out of range in my code?▼

Resolve an IndexError by inspecting the stack trace to find the failing line, reading the source file, applying a minimal fix like a bounds check, and rerunning the failing test to confirm the code error is gone.

Related Skills

Explore More Software Engineering Skills→
ArabelaTsoArabelaTso
142

bug-reproduction-test-generator

Generate executable regression tests from bug reports and stack traces.

Community
Intermediate
cill-i-amcill-i-am

test-driven-development

Write failing tests before implementing minimal production code in a red-green-refactor workflow.

Community
Intermediate
JEO-tech-aiJEO-tech-ai
8

codebase-search

Locate functions and trace calls across large code repositories.

Community
Advanced
michael-harrismichael-harris
17

devteam-bug

Diagnose and fix software bugs through an interview-driven multi-agent workflow.

Community
Advanced