troubleshoot-bug

Investigate GitHub Issues bugs by tracing code paths and querying local logs for root cause analysis.

Updated May 2, 2024
One-click install
npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill troubleshoot-bug-cman131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot-bug
Source: https://github.com/cman131/EatSomethingSourWhenYoureTired/tree/main/.claude/skills/troubleshoot-bug
Command: npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill troubleshoot-bug-cman131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging reported bugs requires manually correlating issue reports, source code, and production logs, which is slow and error-prone. This Skill structures that investigation end-to-end so you reach a root cause faster. ## Core Features & Use Cases - Issue Intake: Fetches the GitHub Issues bug report and comments, then extracts symptoms, scoping identifiers, and a time window. - Code Path Tracing: Greps the source tree for error messages and feature names, traces the call chain from controller to data layer, and collects every log statement along the way. - Tiered Log Queries: Runs scoped grep queries against local logs in three tiers (error overview, specific message templates, chronological entity trace) and cross-checks external dependency failures. - Use Case: A user reports that game verification fails intermittently. Provide the issue ID, and the Skill reads the report, traces the verification endpoint code, queries the last two days of logs filtered by the game ID, and produces a structured root cause report with a recommended fix. ## Quick Start Investigate the bug reported in GitHub issue 3922115 and produce a root cause analysis report.

Frequently Asked Questions about troubleshoot-bug

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

FAQPage Schema
How do I investigate a bug from a GitHub issue using logs?▼

Provide the issue ID or URL as the argument. The Skill fetches the report and comments, extracts scoping identifiers, traces the relevant code path, and runs tiered grep queries against local logs to build a root cause report.

What information do I need before running a bug investigation?▼

You need a GitHub issue ID or URL, plus at least one scoping identifier such as an environment ID, user ID, or entity ID. Without scoping identifiers, log queries risk returning unmanageably large result sets.

Does this work with centralized log platforms like Datadog or Splunk?▼

No, this Skill is configured for console and local logs only, using grep against log files and stdout/stderr. For centralized platforms, you would need to adapt the query tier commands to that platform's query syntax.

What is the default time window for log queries?▼

The default window is the last two days. It narrows to four hours around a specific incident when timestamps appear in the bug report, and only widens to seven days if the two-day window shows nothing and the user confirms.

How are third-party dependency failures investigated without their logs?▼

Failures from unobservable dependencies surface as exception stack traces in this service's own logs. The Skill searches for those traces around the incident window and directs you to the dependency's own console for deeper root cause.