debug-issue

Reproduce, isolate, and resolve application code failures with verification steps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/4asaanAI/Claude-patches --skill debug-issue-4asaanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/4asaanAI/Claude-patches/tree/main/framework-foundry/Claude%20Plugins/layaa-ai/skills/debug-issue
Command: npx skills add https://github.com/4asaanAI/Claude-patches --skill debug-issue-4asaanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable process to diagnose and resolve reported software issues by guiding reproduction, isolation, root cause analysis, code-level fixes, and verification steps.

Core Features & Use Cases

  • Reproduce reliably: Capture exact steps, inputs, environment details, and logs needed to recreate the issue.
  • Isolate across layers: Identify whether the failure stems from frontend components, React Query hooks, edge functions, database queries (Supabase), or LLM/third-party calls.
  • Root cause and fix: Trace data flow and code paths to locate the failure point and propose minimal, targeted code changes to remediate it.
  • Verify and prevent regressions: Define verification steps and regression checks to ensure the fix resolves the issue without side effects.
  • Use Case: Troubleshoot a realtime subscription error in Layaa OS where clients stop receiving updates due to a malformed edge function handler or a broken DB trigger.

Quick Start

Reproduce the failing signup flow in Layaa OS by listing exact steps, inputs, environment variables, and logs, then identify the root cause and propose a minimal code fix.

Frequently Asked Questions about debug-issue

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

FAQPage Schema
How do I systematically debug Supabase edge functions and React Query errors?

To debug Supabase edge functions and React Query errors systematically, capture exact reproduction steps, isolate the failing layer, trace data flow, and propose minimal code fixes with verification checks to prevent regressions.

What's the best way to find the root cause of a broken realtime subscription?

Finding the root cause of a broken realtime subscription requires isolating the failure across frontend components, edge functions, or database queries, then tracing data flow to locate the malformed handler or broken trigger.

How do I reproduce a software bug reliably for root cause analysis?

To reproduce a software bug reliably for root cause analysis, document the exact steps, inputs, environment variables, and logs needed to recreate the issue consistently before attempting any code-level fixes.

Can I isolate frontend component failures from backend endpoint issues during troubleshooting?

Yes, you can isolate frontend component failures from backend endpoint issues by tracing data flow across React Query hooks, edge functions, and Supabase database queries to pinpoint the exact failure layer.

How do I prevent regressions when applying a bug fix to application code?

To prevent regressions when applying a bug fix to application code, define explicit verification steps and regression checks that ensure the minimal targeted code changes resolve the issue without causing side effects.

Do I need logs and code access to troubleshoot LLM integration failures?

Yes, you need access to relevant code and logs to troubleshoot LLM integration failures, as reproducing the issue and tracing data flow through integration points requires detailed environment and input context.