github-issue-investigator

Search GitHub issues and code to diagnose bugs and generate reports.

1|Updated Jul 8, 2022

Search Tags:#developer tools #code analysis #debugging #github issues #bug investigation #reproduction steps

Ready to run

npx skills add https://github.com/jiito/dotfiles --skill github-issue-investigator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-investigator
Source: https://github.com/jiito/dotfiles/tree/main/.agents/skills/github-issue-investigator
Command: npx skills add https://github.com/jiito/dotfiles --skill github-issue-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers and users quickly identify, understand, and document software bugs by leveraging GitHub issues and code analysis.

Core Features & Use Cases

Bug Triage: Automatically searches GitHub for existing issues related to reported bugs.
Code Exploration: Analyzes relevant code sections to pinpoint potential root causes.
Report Generation: Creates detailed investigation reports with reproduction steps and findings.
Use Case: A user reports a bug in a web application. This Skill will search the project's GitHub issues, examine the code related to the reported symptoms, and generate a report detailing whether the bug is known, its likely cause, and how to reproduce it.

Quick Start

Use the github-issue-investigator skill to investigate a bug report about slow loading times in the main dashboard.

Frequently Asked Questions about github-issue-investigator

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 of a bug?▼

To investigate a GitHub issue, you search existing issues and analyze the relevant code repositories to identify potential root causes. The process generates comprehensive investigation reports detailing the likely cause and reproduction steps.

Can I generate bug reproduction steps directly from GitHub issues?▼

Yes, you can generate bug reproduction steps by analyzing data flow and exploring relevant code sections linked to GitHub issues. This process automatically creates detailed investigation reports with clear reproduction steps and findings.

Do I need the GitHub CLI to search issues and analyze code?▼

Yes, you need the GitHub CLI (gh) installed and authenticated to search issues and analyze code. The investigator handles GitHub CLI authentication issues automatically to ensure successful repository exploration and bug triage.

What's the best way to triage known software bugs using GitHub issues?▼

The best way to triage known bugs is to automatically search GitHub issues for existing reports related to your symptoms. This identifies whether the bug is known and examines related code to pinpoint the root cause.

Why does my GitHub bug investigation fail when analyzing a repository?▼

Your GitHub bug investigation may fail due to repository not found errors or GitHub CLI authentication issues. The investigator handles these errors directly, ensuring code exploration and root cause analysis continue without interruption.

Does the github-issue-investigator work for web application bug reports?▼

Yes, the github-issue-investigator works for web application bug reports by searching the project's GitHub issues and examining the code related to the reported symptoms. It outputs a detailed report on whether the bug is known and how to reproduce it.