skills.rest
kishan04rajput
kishan04rajputCOMMUNITY
Explore all skills by this author →
GitHub

identify-bugs

Trace code execution and analyze state to identify root causes of bugs.

1|Updated Jun 14, 2025
Search Tags:#root cause analysis#software quality#rca#debugging workflow#identify bugs#code traversal
One-click install
npx skills add https://github.com/kishan04rajput/ai-ide-rules --skill identify-bugs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: identify-bugs
Source: https://github.com/kishan04rajput/ai-ide-rules/tree/main/global_skills/identify-bugs
Command: npx skills add https://github.com/kishan04rajput/ai-ide-rules --skill identify-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach for identifying and analyzing bugs in code. It focuses on identification, root-cause analysis (RCA), and bug identification, and it explicitly avoids writing or applying fixes.

Core Features & Use Cases

  • Reproduce & Isolate: Establish reproducible steps and minimize the environment to a minimal reproducible example.
  • Code Traversal & Method Analysis: Trace from entry points through call graphs to understand execution flow and locate faulty logic.
  • State & Data Flow Analysis: Track internal state changes and data passed between methods to identify divergence from expected behavior.
  • Concurrency & Resource Analysis: Check for race conditions, resource leaks, or deadlocks in concurrent code paths.
  • Paradigm-Specific Quiddities: Apply language-specific considerations (e.g., Python, JavaScript, Rust) to surface subtle bugs.
  • Understand & Explain (RCA): Identify root causes, categorize bug types, and articulate the issue clearly.
  • Scenario Evaluation: Consider edge cases, inputs, and environments to ensure robust RCA.
  • Verification (Identification Only): Confirm root-cause pinpointing and document risks or related issues.

Quick Start

Use the identify-bugs skill to reproduce and trace a bug in the target module, documenting steps, isolating a minimal environment, and performing root-cause analysis.

Frequently Asked Questions about identify-bugs

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

FAQPage Schema
How do I perform root cause analysis to identify bugs in my code?▼

Root cause analysis for bug identification involves documenting reproducible steps, isolating a minimal environment, tracing execution through call graphs, and analyzing state and data flow to pinpoint the faulty logic.

What is the best way to trace execution flow and find faulty logic across modules?▼

Tracing execution flow requires code traversal from entry points through call graphs. This method helps track internal state changes and data passed between methods to locate where behavior diverges from expectations.

How do I check for race conditions and resource leaks during debugging?▼

Checking for race conditions and resource leaks requires concurrency and resource analysis. You must inspect concurrent code paths to identify deadlocks, resource leaks, or race conditions contributing to the bug.

Does this root cause analysis workflow apply to Python, JavaScript, and Rust?▼

Yes, the root cause analysis workflow applies across modules and languages. It specifically includes paradigm-specific quiddities to surface subtle bugs in languages like Python, JavaScript, and Rust.

Can I use this approach to automatically write and apply fixes for identified bugs?▼

No, this approach explicitly avoids writing or applying fixes. It focuses strictly on identifying bugs, categorizing bug types, verifying the root-cause pinpointing, and articulating the issue clearly through documentation.

Why do I need to isolate a minimal reproducible example for bug identification?▼

Isolating a minimal reproducible example is necessary to establish reliable reproduction steps. Minimizing the environment removes external noise, allowing accurate tracing and state analysis to confirm the root cause.

Related Skills

Explore More Software Engineering Skills→
Oscar-Ivan-SalasOscar-Ivan-Salas

systematic-debugging

Reproduce, isolate, understand, and verify software issues with root-cause analysis.

Community
Advanced
AvatarGanymedeAvatarGanymede

fix

Reproduce software bugs, analyze root causes, and apply minimal fixes with regression tests.

Community
Advanced
evstackevstack
4

evolve-debugger

Record and replay blockchain execution traces for time-travel debugging.

Official
Advanced
Mithrandir21Mithrandir21

android-bug-hunting-stacktrace-analyzer

Analyze Android stack traces to identify exception types and root causes.

Community
Intermediate