skills.rest
hjung3113
hjung3113COMMUNITY
Explore all skills by this author →
GitHub

diagnose

Guide systematic debugging of complex system bugs and performance issues.

Updated Apr 20, 2026
Search Tags:#performance#debugging#troubleshooting#instrumentation#diagnosis#fuzzing#system bugs
One-click install
npx skills add https://github.com/hjung3113/vocpage --skill diagnose-hjung3113
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/hjung3113/vocpage/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/hjung3113/vocpage --skill diagnose-hjung3113

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a disciplined approach to diagnosing hard bugs, performance regressions, and system failures efficiently.

Core Features & Use Cases

  • Offers a structured, step-by-step process to reproduce and analyze difficult bugs.
  • Guides users in constructing feedback loops, hypotheses, and targeted instrumentation.
  • Useful for debugging system crashes, slowdowns, or elusive errors in development or production environments.
  • Example: A developer suspects a recent change caused a performance drop and uses this Skill to methodically identify the root cause.

Quick Start

Run the diagnostic process with a focused test harness to locate and analyze challenging bugs in the system.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically debug complex system bugs and performance regressions?▼

To debug complex system bugs and performance regressions, use a structured process to reproduce failures, form hypotheses, instrument code, and verify fixes. This isolates root causes across development and production setups.

What is the best way to troubleshoot elusive performance slowdowns in production?▼

Troubleshooting performance slowdowns requires building targeted feedback loops and instrumenting code to capture runtime data. This methodical diagnosis identifies whether recent system changes triggered the failure or latency.

Can I use systematic diagnosis for both development and production environments?▼

Yes, systematic diagnosis applies to both development and production environments. It guides software engineers through reproducing failures and verifying fixes across different setups to handle intricate troubleshooting scenarios.

How do I form hypotheses when fuzzing fails to reproduce a system crash?▼

When fuzzing fails to reproduce a system crash, form hypotheses by instrumenting code around suspected failure points. This targeted feedback loop analyzes challenging bugs by capturing the exact runtime conditions triggering the error.

When should I avoid a methodical debugging approach for system bugs?▼

Avoid a methodical debugging approach for system bugs when issues are trivial or have obvious immediate fixes. It is designed for software engineers handling intricate troubleshooting scenarios and complex regressions requiring deep analysis.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
hopeoverturehopeoverture
6

sentry-and-otel-setup

Configure Sentry and OpenTelemetry error tracking and performance monitoring for Next.js applications.

Community
Advanced
bossjonesbossjones
1

diagnose

Guide systematic debugging with reproducibility, hypothesis generation, and regression testing.

Community
Advanced