debug-issue

Troubleshoot OMS system issues with a structured debugging workflow.

16|9|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/omni-system-creator/omni --skill debug-issue-omni-system-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-issue
Source: https://github.com/omni-system-creator/omni/tree/main/.claude/skills/debug-issue
Command: npx skills add https://github.com/omni-system-creator/omni --skill debug-issue-omni-system-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable approach to identifying and solving issues within the OMS system, reducing mean time to resolution and manual effort.

Core Features & Use Cases

  • Structured debugging workflow covering information gathering, layer identification (frontend, backend, database)
  • Systematic checks for common issues (OrgId filtering, authentication, API responses, routing)
  • Practical, reproducible steps and best practices for diagnosing and fixing OMS problems across environments
  • Use Case: When a user reports an error, run through the steps to gather details, isolate the layer, and implement a fix with verification

Quick Start

Describe the issue clearly to trigger the structured debugging workflow and begin the step-by-step diagnostic process.

Frequently Asked Questions about debug-issue

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

FAQPage Schema
How do I debug OMS system errors across different application layers?

Debug OMS system errors by following a structured debugging workflow that covers information gathering, layer identification across frontend, backend, and database, and systematic checks to isolate and resolve the issue.

What is the best way to troubleshoot OrgId filtering and authentication issues in OMS?

Troubleshoot OMS OrgId filtering and authentication issues using systematic diagnostic checks that validate API responses, routing configurations, and layer-specific behaviors to identify the root cause.

How do I start diagnosing a reported OMS error when I only have a vague problem statement?

Start diagnosing a reported OMS error by describing the issue clearly to trigger the structured debugging workflow, which then guides you through step-by-step information gathering and layer isolation.

What information do I need before troubleshooting an OMS system issue?

Troubleshooting an OMS system issue requires a clear problem statement and reproducible steps to initiate the diagnostic process and ensure the resolution can be validated for a durable fix.

Why does my OMS debugging workflow fail to produce a durable fix?

OMS debugging fails to produce a durable fix when the workflow lacks validated resolutions, meaning the fix was not confirmed through reproducible steps and systematic checks across the application layers.