investigate-bug

Investigate GitHub issues to identify root causes and affected files.

1|Updated Jan 19, 2026

Search Tags:#investigate #root-cause #issue-management #bug #github-issues #code-discovery #investigation-report

Ready to run

npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill investigate-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate-bug
Source: https://github.com/VIPER-Metrics/claude-code-skills/tree/main/skills/investigate-bug
Command: npx skills add https://github.com/VIPER-Metrics/claude-code-skills --skill investigate-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Bug Investigation Agent helps developers quickly gather context, reproduce steps, identify root causes, and document an investigation report for GitHub issues before implementing fixes.

Core Features & Use Cases

Validation & data extraction: Fetch and validate issue details from GitHub, extract error messages, steps to reproduce, and affected files.
Code path discovery: Trace the call paths, read involved files, and map error propagation to the root cause.
Investigation report generation: Create a structured investigation report and post it to the GitHub issue.

Quick Start

Use the /investigate-bug {issue_number} command to begin the investigation.

Frequently Asked Questions about investigate-bug

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

FAQPage Schema

How do I investigate a GitHub issue to find the root cause?▼

To investigate a GitHub issue for root cause, you fetch issue data via gh, extract error messages and reproduction steps, trace code paths, and generate a structured investigation report posted back to the issue.

What's the best way to map code paths affected by a bug?▼

Mapping code paths affected by a bug involves reading involved files, tracing call paths, and mapping error propagation to pinpoint the root cause, which produces a structured investigation report for the GitHub issue.

Can I automatically post an investigation report to a GitHub issue?▼

Yes, you can automatically post an investigation report to a GitHub issue. The process reads issue data via gh, analyzes the code paths, and generates a structured report directly back to the GitHub issue thread.

Do I need the gh CLI to extract error messages from GitHub issues?▼

Yes, you need the gh CLI to extract error messages. Reading issue data via gh is required to fetch and validate issue details, extract reproduction steps, and identify affected files for the investigation.

What is included in a bug investigation report for GitHub issues?▼

A bug investigation report includes the identified root cause, affected files, scope of the issue, mapped code paths, and extracted error messages, providing a structured document posted directly to the GitHub issue.

How do I trace error propagation to identify affected files?▼

Tracing error propagation to identify affected files requires reading involved files and mapping the call paths from the extracted error messages, ultimately documenting the root cause and scope in an investigation report.