debugging

Diagnose and fix bugs in the Supplier Management System codebase.

Updated Oct 3, 2025
One-click install
npx skills add https://github.com/jobayerarman/Supplier_Management_System --skill debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/jobayerarman/Supplier_Management_System/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/jobayerarman/Supplier_Management_System --skill debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging can be a time-consuming and frustrating process, often involving repetitive steps to identify, reproduce, and fix issues. This Skill provides a structured, systematic workflow to diagnose bugs, pinpoint root causes, implement fixes, and rigorously verify solutions, significantly reducing debugging time and effort for developers.

Core Features & Use Cases

  • Systematic Root Cause Analysis: Guides through symptom collection, environment analysis, unit/integration testing, and deep code tracing to find the exact cause of an issue.
  • Fix Implementation & Verification: Helps design minimal, targeted fixes, implement them, and rigorously verify that the bug is resolved without introducing regressions.
  • Prevention Test Case Generation: Encourages creating new test cases that would catch the identified bug, preventing its recurrence in the future.
  • Use Case: When a user reports "the balance is wrong after a partial payment," the AI can activate this skill to systematically investigate, identify the exact code error, suggest a fix, and ensure all tests pass before deployment.

Quick Start

I have a bug: the balance is not updating correctly after a partial payment. Please help me debug it.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I systematically debug a bug when I don't know where to start?

Systematic debugging begins by collecting symptoms, analyzing the environment and context where the bug occurs, then writing targeted unit and integration tests to reproduce it. This structured approach pinpoints root cause through deep code tracing and iterative fixes, reducing guesswork and debugging time.

What's the best way to identify the root cause of a data integrity issue or concurrency problem?

Root cause analysis combines symptom collection, environment inspection, and comprehensive logging to trace data integrity and concurrency issues. Deep code tracing with targeted tests isolates the exact failure point, enabling minimal fixes that resolve the issue without introducing regressions.

How do I verify that my bug fix actually works and won't break other code?

Verification involves executing unit and integration tests after implementing your fix to confirm the bug is resolved and no regressions were introduced. Creating new test cases that would have caught the original bug prevents its recurrence and documents the fix.

Can I use this debugging approach for application slowdowns and performance failures?

Yes, this workflow applies to slowdowns and performance failures alongside code errors and data issues. The same symptom collection, environment analysis, deep tracing, and iterative testing process identifies bottlenecks and performance root causes.

What should I document when fixing a bug to prevent it happening again?

Document your fix by creating reproducible reproduction steps, comprehensive logging records, and new test cases that catch the identified bug. This creates a preventive record and enables team members to understand the issue and its solution.