skills.rest
bkywksj
bkywksjCOMMUNITY
Explore all skills by this author →
GitHub

bug-detective

Diagnose and locate root causes of software bugs across codebases.

309|58|Updated Apr 16, 2026
Search Tags:#typescript#debugging#troubleshooting#rust#root-cause#log-analysis#bug-diagnosis
One-click install
npx skills add https://github.com/bkywksj/knowledge-base --skill bug-detective-bkywksj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-detective
Source: https://github.com/bkywksj/knowledge-base/tree/main/.claude/skills/bug-detective
Command: npx skills add https://github.com/bkywksj/knowledge-base --skill bug-detective-bkywksj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to diagnosing and locating the root causes of software bugs across codebases, reducing time to fix and improving debugging consistency.

Core Features & Use Cases

  • Systematic repro and data collection: gather error messages, logs, and reproduction steps to establish a clear problem statement.
  • Narrowing scope and root-cause localization: guide you through isolating whether the issue is frontend, backend, or IPC, and identify failing components.
  • Verification and documentation: provide a checklist to validate fixes and document the resolution for future reference.
  • Use Case: When a Rust backend panics or a TypeScript frontend bug occurs, follow this guide to reproduce, isolate, and confirm a fix.

Quick Start

Describe the issue, collect logs and steps to reproduce, then follow the guide to locate and verify the root cause and fix.

Frequently Asked Questions about bug-detective

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

FAQPage Schema
How do I systematically locate the root cause of a bug in a Rust backend?▼

To debug a TypeScript frontend, start by collecting reproduction steps and relevant logs to formulate a precise problem statement. Then, follow a structured methodology to narrow the scope, isolate the failing frontend component, and verify the applied fix.

What is the best way to isolate whether a bug is in the frontend, backend, or IPC layer?▼

The best way to isolate a bug across frontend, backend, or IPC layers is to use a structured narrowing methodology that guides you through component-level checks. This approach systematically identifies the exact failing area during your root-cause investigation.

How do I structure log analysis for troubleshooting a software bug?▼

To structure log analysis for troubleshooting, aggregate error messages and reproduction steps to establish a clear problem statement. This systematic data collection methodically isolates the root cause and verifies the fix across Rust or TypeScript components.

Can I use a systematic debugging methodology for both Rust and TypeScript codebases?▼

Yes, you can apply this systematic debugging methodology to both Rust and TypeScript codebases. It provides a repeatable approach to reproduce, isolate, and verify bug fixes, improving consistency during cross-component bug investigations and log analysis.

What should I do after isolating a root cause to verify the bug fix?▼

After isolating a root cause, you should use a verification checklist to validate the bug fix and document the resolution. This final step in the debugging process ensures the fix is confirmed and provides reference material for future troubleshooting.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
112

Create Jira Bug

Create Jira bug reports with reproduction steps and environment details.

Community
Basic
ariaxhanariaxhan
12

debug

Reproduce bugs with exact steps and isolate root causes using controlled tests.

Community
Advanced
Ab-aswiniAb-aswini
2

systematic-debugging

Guide users through a 4-phase debugging process for complex software issues.

Community
Intermediate
R2W1csR2W1cs
1

lint-and-validate

Lint and validate JavaScript and Python code for syntax and style issues.

Community
Intermediate