issue

Analyze bugs, detect root causes, and create structured GitHub issues.

10|5|Updated Apr 10, 2026

Search Tags:#debugging #root cause analysis #bug investigation #issue creation #gitHub

Ready to run

npx skills add https://github.com/rajitsaha/100x-dev --skill issue-rajitsaha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/rajitsaha/100x-dev/tree/main/modules/issue
Command: npx skills add https://github.com/rajitsaha/100x-dev --skill issue-rajitsaha

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps engineering teams conduct thorough investigations of bugs or gaps, ensuring root causes are identified and documented comprehensively.

Core Features & Use Cases

In-Depth Analysis: Guides users through multi-phase investigations analyzing code, data, architecture, and impact.
Root Cause Identification: Assists in pinpointing precise causes with supporting details and associated files.
Actionable Documentation: Automates the creation of detailed, structured GitHub issues for tracking and resolution planning.
Use Case: When a bug is reported, a developer uses this Skill to analyze the problem thoroughly and generate a complete issue report for the team.

Quick Start

Describe the observed bug or gap; the skill will generate a detailed investigation plan and issue report.

Frequently Asked Questions about issue

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

FAQPage Schema

How do I conduct thorough bug investigation and root cause analysis for my codebase?▼

Thorough bug investigation requires multi-phase analysis of code, data, and architecture to pinpoint precise root causes. This skill guides that process, providing supporting details and associated files to improve engineering troubleshooting workflows.

How do I automate GitHub issue creation after a bug investigation?▼

Automating GitHub issue creation involves transforming detailed investigation findings into structured documentation. This skill generates complete, actionable issue reports integrating with GitHub to streamline your incident management and resolution planning.

What is the best way to document a root cause analysis for an engineering team?▼

Documenting root cause analysis effectively means recording precise causes, associated files, and impact assessments. This skill automates the creation of detailed, structured documentation to ensure engineering teams track and resolve incidents comprehensively.

How do I perform risk and impact assessment when a bug is reported?▼

Performing risk and impact assessment requires a multi-phase investigation analyzing architecture and data behavior. This skill facilitates comprehensive bug analysis, supporting detailed risk assessment to understand the full scope of the reported issue.

Does this bug investigation approach work without external dependencies?▼

Yes, this bug investigation approach works without external dependencies, requiring only a description of the observed gap or bug. It independently generates an investigation plan and issue report using its internal scripts and references.