skills.rest
gaebalai
gaebalaiCOMMUNITY
Explore all skills by this author →
Website𝕏@gaebalaiGitHub

incident-debug

Cross-analyze logs, code, and Git history to identify root causes.

2|Updated Feb 25, 2026
Search Tags:#debugging#root cause analysis#log analysis#incident response#code tracing#production issues
One-click install
npx skills add https://github.com/gaebalai/claude-code-kit-ko --skill incident-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incident-debug
Source: https://github.com/gaebalai/claude-code-kit-ko/tree/main/.claude/skills/incident-debug
Command: npx skills add https://github.com/gaebalai/claude-code-kit-ko --skill incident-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you systematically investigate and pinpoint the root cause of critical production incidents or bugs by analyzing logs, code, and Git history.

Core Features & Use Cases

  • Comprehensive Analysis: Cross-references logs, code, and Git history to identify the root cause.
  • Root Cause Identification: Pinpoints the exact source of the problem.
  • Recovery & Prevention: Proposes immediate fixes and long-term preventative measures.
  • Use Case: When a critical bug is reported in production, use this Skill to analyze the error logs, trace the faulty code, and identify the specific commit that introduced the issue, then get a plan for hotfixes and permanent solutions.

Quick Start

Use the incident-debug skill to analyze the provided error log and propose a recovery plan.

Frequently Asked Questions about incident-debug

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

FAQPage Schema
How do I find the root cause of a production incident from error logs?▼

To find the root cause of a production incident, cross-analyze error logs with code and Git history to pinpoint the exact source. This approach identifies the specific commit that introduced the issue and provides a comprehensive incident timeline.

What is the best way to trace a critical bug back to its source code commit?▼

The best way to trace a critical bug to its source code commit is by cross-referencing error logs with code tracing and Git history. This method pinpoints the exact faulty code commit that introduced the production issue.

Can I use log analysis to get both temporary fixes and long-term solutions for critical bugs?▼

Yes, log analysis can generate a comprehensive report detailing both temporary fixes and long-term solutions for critical bugs. It cross-references logs and code to propose immediate recovery and preventative measures.

Does incident response debugging work with just a symptom description or URL?▼

Incident response debugging supports analysis of error logs, symptoms, or URLs, with optional time and environment details. It investigates production issues by cross-analyzing these inputs with code and Git history to identify the root cause.

What should be included in a comprehensive incident response report for production issues?▼

A comprehensive incident response report for production issues should include the incident overview, timeline, log analysis, root cause, temporary fixes, and long-term solutions. This ensures complete recovery and prevention tracking.

Related Skills

Explore More Software Engineering Skills→
FlintmereFlintmere

debug-prod-incident

Trace production incidents into evidence-backed timelines and root-cause hypotheses.

Official
Advanced
Draft-OfficialDraft-Official

systematic-debugging

Diagnose software bugs through four investigative phases for root cause analysis.

Official
Advanced
rnavarychrnavarych
14

alpha-core:observability

Set up structured logging, metrics collection, and distributed tracing with ELK, Prometheus, Grafana, Datadog, and OpenTelemetry.

Community
Advanced
NotysotyNotysoty
9

Bug Root Cause Analyzer

Trace stack traces and generate structured root-cause reports for software bugs.

Community
Advanced