skills.rest
fall-out-bug
fall-out-bugCOMMUNITY
Explore all skills by this author →
GitHub

issue

Analyzes bug reports, assigns severity P0-P3, and recommends /fix actions.

19|Updated Dec 28, 2025
Search Tags:#debugging#hotfix#bugfix#bug analysis#severity classification#issue routing
One-click install
npx skills add https://github.com/fall-out-bug/sdp --skill issue-fall-out-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/fall-out-bug/sdp/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/fall-out-bug/sdp --skill issue-fall-out-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of analyzing reported bugs, accurately classifying their severity, and directing them to the most appropriate resolution command or workflow.

Core Features & Use Cases

  • Systematic Debugging: Follows a structured 5-phase process to isolate the root cause of issues.
  • Severity Classification: Assigns a priority level (P0-P3) based on the impact of the bug.
  • Intelligent Routing: Determines whether a bug requires an immediate /hotfix, a standard /bugfix, or should be deferred to the backlog.
  • Use Case: When a user reports a critical production error, this Skill will analyze the provided logs, classify it as P0, and suggest running the /hotfix command.

Quick Start

Analyze the bug described in the provided error log file.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I analyze a reported bug and isolate the root cause?▼

To analyze a reported bug and isolate the root cause, this skill follows a structured 5-phase debugging workflow that includes hypothesis formation, elimination, and systematic root cause isolation.

What is the best way to classify bug severity from P0 to P3?▼

The best way to classify bug severity from P0 to P3 is by evaluating the bug's impact, which allows the system to accurately assign priority levels and determine if an immediate hotfix is required.

How does bug routing work for hotfixes versus standard bugfixes?▼

Bug routing for hotfixes versus standard bugfixes works by generating an issue file with routing recommendations, directing critical bugs to an immediate hotfix, standard bugs to a bugfix, and minor bugs to the backlog.

Can I use error logs to trigger an automated debugging workflow?▼

Yes, you can use error logs to trigger an automated debugging workflow, as the skill systematically analyzes provided log files to classify severity and route the issue to the appropriate fix command.

When do I need to defer a bug fix to the backlog instead of hotfixing?▼

You need to defer a bug fix to the backlog instead of hotfixing when the severity classification evaluates the bug's impact as low priority (P2-P3), indicating it does not require immediate resolution.

Related Skills

Explore More Software Engineering Skills→
FlintmereFlintmere

fix-bug

Reproduce reported defects in Flintmere's codebase and validate fixes with regression tests.

Official
Advanced
viraatdasviraatdas

investigate

Identify bug root causes by collecting symptoms, reading code, and testing hypotheses.

Community
Advanced
JamkrisJamkris
86

ai-regression-testing

Run sandbox-mode regression tests to prevent AI-induced code regressions.

Community
Advanced
managedcodemanagedcode
4

mcaf-dotnet-roslynator

Integrate Roslynator analyzers into .NET projects for C# static analysis and auto-fixing.

Official
Intermediate