debugging

Diagnose Python software defects using systematic elimination phases.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/kollaborai/kollab --skill debugging-kollaborai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/kollaborai/kollab/tree/main/bundles/skills/debugging
Command: npx skills add https://github.com/kollaborai/kollab --skill debugging-kollaborai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured, ad-hoc bug fixing wastes development time and often introduces new defects. This skill enforces a proven systematic elimination methodology to diagnose and resolve bugs efficiently while minimizing unintended side effects.

Core Features & Use Cases

  • Phased Debugging Workflow: Covers environment verification, root cause analysis, print debugging, debugger usage, log analysis, git bisect for regressions, memory debugging, performance profiling, and concurrency debugging.
  • Use Case: A developer experiencing intermittent race conditions in an async Python application can follow the concurrency debugging phase to add thread-aware logging, identify lock ordering issues, and implement a fix without disrupting other functionality.

Quick Start

Activate the debugging skill and follow the systematic elimination phases to diagnose and resolve the reported application bug.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I fix intermittent race conditions in an async Python application?

Systematic bug fixing prevents new defects by enforcing a phased elimination methodology for diagnosing software issues. This structured approach replaces ad-hoc debugging with environment verification, root cause analysis, and targeted profiling to resolve defects efficiently.

How do I use git bisect to find regression bugs in Python?

Git bisect automates regression bug identification by systematically narrowing down commits that introduced the defect. You activate the debugging workflow to follow the phased elimination methodology, using git bisect automation to pinpoint the exact code change causing the regression.

What is the best way to find memory leaks and performance bottlenecks in Python?

Memory debugging and performance profiling identify bottlenecks and leaks by analyzing application resource usage over time. The systematic elimination methodology guides you through profiler operation and memory analysis to isolate the exact memory leak or performance bottleneck.

Can I use this systematic debugging workflow for production environment crashes?

Yes, the systematic debugging methodology supports diagnosing application crashes across local, development, and production environments. It provides integrated guidance for log analysis and debugger operation suitable for resolving production software defects without unintended side effects.

Why does unstructured ad-hoc bug fixing introduce new software defects?

Unstructured bug fixing introduces new defects because it lacks systematic verification and root cause analysis. Without a phased elimination methodology covering environment verification and regression testing, code changes often create unintended side effects that generate additional software bugs.