skills.rest
marktantongco
marktantongcoCOMMUNITY
Explore all skills by this author →
GitHub

diagnose

Diagnose software problems using structured workflows and root cause analysis.

Updated May 3, 2026
Search Tags:#debugging#root cause#error analysis#diagnosis#performance profiling
One-click install
npx skills add https://github.com/marktantongco/remotion-video-pro --skill diagnose-marktantongco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/marktantongco/remotion-video-pro/tree/main/skills/diagnose
Command: npx skills add https://github.com/marktantongco/remotion-video-pro --skill diagnose-marktantongco

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a systematic approach to identifying, analyzing, and resolving software problems, streamlining the debugging process.

Core Features & Use Cases

  • Structured Diagnostic Workflows: Combines domain-specific knowledge with structured workflows for efficient problem-solving.
  • Error Classification: Categorizes errors into syntax, runtime, logic, integration, performance, security, configuration, concurrency, and resource issues.
  • Root Cause Analysis: Utilizes techniques like the 5 Whys, Fishbone Diagrams, and Fault Tree Analysis to pinpoint the root cause of problems.
  • Log Analysis: Offers guidance on reading and interpreting stack traces, identifying patterns, and diagnosing performance issues.
  • Performance Diagnosis: Provides strategies for profiling and identifying common performance pitfalls.
  • Diagnostic Decision Tree: Offers a step-by-step guide to diagnose common software issues.
  • Known Pitfalls Reference: Lists common pitfalls in various programming languages and databases.

Quick Start

Use the diagnose skill to analyze a stack trace from a recent application crash.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is the best way to analyze a stack trace from an application crash?▼

Analyzing a stack trace is best done using a structured diagnostic workflow that interprets logs, classifies runtime errors, and applies root cause analysis to pinpoint the exact failure point.

How do I find the root cause of a software bug?▼

To find the root cause of a software bug, apply systematic techniques like the 5 Whys, Fishbone Diagrams, and Fault Tree Analysis to move past symptoms and identify the underlying logic or integration failure.

How can I profile application performance issues?▼

Profiling application performance issues requires a structured diagnostic workflow that identifies common performance pitfalls, analyzes resource usage, and isolates bottlenecks causing system degradation.

What are the common types of software errors I should look for during debugging?▼

Common software errors to look for during debugging include syntax, runtime, logic, integration, performance, security, configuration, concurrency, and resource issues, each requiring specific diagnostic strategies.

How do I use a diagnostic decision tree for troubleshooting software problems?▼

Using a diagnostic decision tree for troubleshooting software problems involves following a step-by-step guide that categorizes error types and systematically narrows down potential root causes through logical branching.

Do I need prior knowledge of software debugging principles to diagnose issues effectively?▼

Yes, effectively diagnosing issues requires foundational knowledge of software debugging principles and practices to correctly interpret logs, apply root cause analysis, and navigate structured diagnostic workflows.

Related Skills

Explore More Software Engineering Skills→
CUexterCUexter
2

systematic-debugging

Identify root causes of bugs through four structured debugging phases.

Community
Advanced
dakshrawat298-gifdakshrawat298-gif

security-fix-review

Review security patches for root-cause coverage and bypass risks.

Community
Intermediate
mvillmowmvillmow
18

analyze-ci-failure-logs

Analyze CI failure logs to identify root causes and error patterns.

Community
Intermediate
TimHL5TimHL5

canary

Monitor post-deploy web apps for console errors, performance metrics, and page failures.

Community
Advanced