debug-issue

Diagnose software bugs by analyzing code, logs, and test failures.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/yuridefranca/ai-prompts --skill debug-issue-yuridefranca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/yuridefranca/ai-prompts/tree/main/src/skills/debug-issue
Command: npx skills add https://github.com/yuridefranca/ai-prompts --skill debug-issue-yuridefranca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers find the root cause of software defects by systematically analyzing code, logs, test failures, and runtime behavior so that incidents are resolved accurately and efficiently.

Core Features & Use Cases

  • Systematic Triage: Collects and interprets error messages, stack traces, and recent changes to narrow the scope of investigation.
  • Code and Log Analysis: Reviews relevant code paths and log artifacts to identify likely fault points and reproduce failures.
  • Actionable Remediation: Produces a clear root-cause explanation, reproduction steps, prioritized fixes, and suggested code changes for pull requests or hotfixes.
  • Use Case: When a user reports a production error or a CI test starts failing, use this Skill to determine the failing component, reproduce the issue locally, and propose a safe fix.

Quick Start

Use the debug-issue skill to analyze the reported error, examine related logs and code files, and produce a root-cause diagnosis with recommended fixes.

Frequently Asked Questions about debug-issue

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

FAQPage Schema
How do I find the root cause of a failing CI job or production error?

To diagnose software bugs and find the root cause of failing CI jobs, you analyze stack traces, logs, and recent code changes. This skill systematically triages those artifacts to narrow the investigation scope and identify the exact fault point.

What is the best way to debug code from user-reported error reports?

Debugging code from user-reported error reports requires reviewing relevant code paths and log artifacts to reproduce the failure. This systematic triage process delivers a clear root-cause explanation, reproduction steps, and suggested code fixes for hotfixes.

Does this debugging approach work with both frontend and backend repositories?

Yes, this debugging approach works with both frontend and backend repositories. It analyzes runtime traces, test failures, and code paths across different repository types to systematically diagnose bugs during development and triage workflows.

How do I generate reproduction steps and code fixes for a triaged bug?

To generate reproduction steps and code fixes for a triaged bug, you examine log artifacts and code paths to pinpoint the failure. This analysis yields prioritized remediation steps and suggested code changes compatible with version control workflows.

Can I use root cause analysis for local test failures and development triage?

Yes, you can use root cause analysis for local test failures and development triage. By interpreting error messages and runtime traces, the process identifies likely fault points and proposes safe fixes for immediate remediation.