debug

Analyze logs and correlate events to categorize software issues.

77|4|Updated Jun 20, 2022
One-click install
npx skills add https://github.com/htlin222/dotfiles --skill debug-htlin222
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/htlin222/dotfiles/tree/main/claude.symlink/skills/debug
Command: npx skills add https://github.com/htlin222/dotfiles --skill debug-htlin222

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you systematically identify, analyze, and resolve errors, test failures, and unexpected behavior in software.

Core Features & Use Cases

  • Log Analysis: Analyze log patterns to pinpoint error spikes and types.
  • Correlation: Run SQL queries to correlate issues across different services.
  • Stack Trace Deep Dive: Perform in-depth analysis of stack traces for complex issues.
  • Use Case: When users report intermittent errors, use this Skill to analyze logs, correlate error messages with specific requests using request IDs, and pinpoint the root cause in the codebase.

Quick Start

Use the debug skill to analyze recent errors in the application logs.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I analyze stack traces to find the root cause of software errors?

Log analysis identifies error spikes and types by analyzing log patterns to pinpoint unexpected behavior. It correlates error messages with specific requests using request IDs to find root causes.

Can I correlate errors across different services using SQL queries?

SQL queries correlate issues across different services by matching request IDs and log entries. This systematic correlation helps diagnose intermittent errors and pinpoint root causes in the codebase.

What is the best way to troubleshoot intermittent application errors?

Troubleshooting intermittent errors requires analyzing logs, correlating error messages with specific requests using request IDs, and performing stack trace analysis to pinpoint the root cause in the codebase.

How do I categorize software issues during debugging to choose the right resolution path?

Debugging categorizes software issues into bug, build, performance, or deployment types to guide resolution. This systematic categorization helps identify, analyze, and resolve unexpected behavior efficiently.

Does this debugging approach work for test failures and deployment issues?

Debugging systematically identifies, analyzes, and resolves test failures and deployment issues. It supports log pattern analysis and stack trace deep dives to diagnose and resolve various software problems.