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

bug-triage

Analyze error logs and Git history to generate bug hypotheses and troubleshooting plans.

2|Updated Feb 25, 2026
Search Tags:#code review#debugging#troubleshooting#log analysis#error analysis#bug triage
One-click install
npx skills add https://github.com/gaebalai/claude-code-kit-ko --skill bug-triage-gaebalai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-triage
Source: https://github.com/gaebalai/claude-code-kit-ko/tree/main/.claude/skills/bug-triage
Command: npx skills add https://github.com/gaebalai/claude-code-kit-ko --skill bug-triage-gaebalai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers quickly identify the root cause of bugs by systematically analyzing error logs and recent code changes, reducing debugging time.

Core Features & Use Cases

  • Log Analysis: Parses error logs and exception messages to pinpoint the error type and location.
  • Code Impact Assessment: Reviews recent Git history to identify potentially problematic code modifications.
  • Root Cause Hypothesis: Generates plausible causes for the bug with supporting evidence.
  • Troubleshooting Plan: Outlines a step-by-step procedure to confirm or rule out the hypothesized causes.
  • Use Case: When a critical error occurs in production, use this Skill with the error log to get a prioritized list of potential causes and a clear plan to investigate them.

Quick Start

Use the bug-triage skill with the provided error log file 'error.log' to analyze the bug.

Frequently Asked Questions about bug-triage

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

FAQPage Schema
How do I analyze error logs to find the root cause of a software bug?▼

To analyze error logs for root causes, parse exception messages to pinpoint the error type and location, then review recent Git history to identify problematic code modifications and generate hypotheses.

What is the best way to triage bugs using recent commit history?▼

Bug triage using commit history involves reviewing recent code modifications to assess their impact on the error, generating plausible root cause hypotheses with supporting evidence.

Can I use this for initial debugging of production errors?▼

Yes, you can use this for initial debugging of production errors by providing the error log file to get a prioritized list of potential causes and a structured investigation plan.

How do I create a troubleshooting plan for exception messages?▼

Create a troubleshooting plan for exception messages by systematically reviewing error details and relevant code sections to outline a step-by-step procedure to confirm or rule out hypothesized causes.

What are the limitations of evidence-based bug triage?▼

Evidence-based bug triage is designed for initial assessment and generating hypotheses, meaning it provides a structured investigation plan rather than directly patching the identified code modifications.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
leanbusqtsleanbusqts
2

troubleshoot

Reproduce, isolate, and determine root causes of software bugs.

Community
Basic
jugrajsinghjugrajsingh
1

diagnosing

Diagnose software errors by gathering evidence and testing hypotheses.

Community
Intermediate
mvillmowmvillmow
18

analyze-ci-failure-logs

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

Community
Intermediate