bug-investigation

Investigate user-reported bugs with root cause analysis and prioritized fix proposals.

93|15|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/nokonoko1203/claude-code-settings --skill bug-investigation-nokonoko1203
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-investigation
Source: https://github.com/nokonoko1203/claude-code-settings/tree/main/symlinks/codex/skills/bug-investigation
Command: npx skills add https://github.com/nokonoko1203/claude-code-settings --skill bug-investigation-nokonoko1203

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill systematically investigates user-reported bugs, providing detailed root cause analysis and actionable solutions to improve software quality.

Core Features & Use Cases

  • Automated Bug Triage: Analyzes symptoms, identifies related code, and visualizes processing flows.
  • Root Cause Analysis: Pinpoints the origin of bugs through code inspection and error mapping.
  • Report Generation: Creates comprehensive bug reports in Japanese, including recommended fixes and priority assessments.
  • Use Case: When a user reports a login failure, this Skill can trace the authentication flow, identify the faulty code, and suggest a fix.

Quick Start

Use the bug investigation skill to analyze the reported issue with the description 'User cannot log in after password reset'.

Frequently Asked Questions about bug-investigation

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

FAQPage Schema
How do I systematically investigate a software bug and find its root cause?

To systematically investigate a software bug, use an automated triage process that analyzes reported symptoms, maps error messages to code, inspects processing flows, and pinpoints the faulty code to identify the root cause.

What is the best way to analyze code for an issue resolution when a user reports a login failure?

The best way to analyze code for issue resolution is to trace the specific processing flow, such as the authentication sequence, map the error messages, and inspect the related code to identify the exact origin of the login failure.

Does bug investigation require specific dependencies to perform root cause analysis?

No specific dependencies are required to perform root cause analysis; the skill operates independently using internal scripts and references, utilizing MCP for efficient code investigation and semantic search.

How do I generate a comprehensive bug report with recommended fixes and priority assessments?

To generate a comprehensive bug report with recommended fixes, run an automated analysis that includes symptom details, flow diagrams, error mappings, code inspection, and prioritized fix proposals based on the identified root cause.

Can I use semantic search to trace an authentication flow and identify faulty code?

Yes, you can use semantic search via MCP to efficiently trace an authentication flow, inspect the related code, and identify the exact faulty code causing the issue.

What should I do if my code analysis is not working to find the origin of a bug?

If your code analysis is not working to find the origin of a bug, utilize an automated root cause analysis process that maps error messages, visualizes processing flows, and inspects code to pinpoint the fault.