skills.rest
Jurel89
Jurel89COMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnose copilot-omni session issues by analyzing logs and inspecting state.

Updated Apr 10, 2026
Search Tags:#debugging#issue resolution#session diagnostics#workflow troubleshooting#copilot-omni
One-click install
npx skills add https://github.com/Jurel89/copilot-omni --skill debug-jurel89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Jurel89/copilot-omni/tree/main/skills/debug
Command: npx skills add https://github.com/Jurel89/copilot-omni --skill debug-jurel89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users quickly diagnose and resolve issues within their copilot-omni sessions, ensuring smooth operation and productivity.

Core Features & Use Cases

  • Log Analysis: Analyze logs to identify the root cause of issues.
  • State Inspection: Inspect the state of the session or repository to understand the context.
  • Reproduction: Reproduce issues to confirm and understand their nature.
  • Root Cause Identification: Identify the root cause of issues and provide a hypothesis.
  • Actionable Recommendations: Offer the smallest next fix or verification step.
  • Use Case: When a user encounters a workflow breakage or confusing runtime behavior in their copilot-omni session, this skill helps them find the real failure signal and the next corrective step.

Quick Start

Use the debug skill to diagnose an issue in your copilot-omni session by providing a description of the problem.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I troubleshoot copilot-omni session workflow breakages?▼

To troubleshoot copilot-omni session workflow breakages, describe the problem to trigger diagnostics that analyze logs, inspect session state, and reproduce issues to pinpoint the root cause.

What is the best way to diagnose runtime behavior issues in copilot-omni sessions?▼

Diagnosing runtime behavior issues in copilot-omni sessions involves analyzing logs and inspecting repository state to find the real failure signal and determine the next corrective step.

How does session state inspection help identify root causes in copilot-omni?▼

Session state inspection in copilot-omni helps identify root causes by providing the repository and session context needed to understand workflow breakages and confirm runtime issues.

Can I reproduce issues to confirm workflow breakages in copilot-omni?▼

Yes, you can reproduce issues to confirm workflow breakages in copilot-omni sessions, allowing the diagnostic process to understand the problem's nature and offer the smallest next verification step.

What should I do when copilot-omni troubleshooting does not find a clear failure signal?▼

When copilot-omni troubleshooting does not find a clear failure signal, provide a detailed description of the confusing runtime behavior to help the diagnostics identify a root cause hypothesis and actionable recommendations.

Related Skills

Explore More Software Engineering Skills→
Jurel89Jurel89

cancel

Detect and cancel active copilot-omni modes with dependency-aware state cleanup.

Community
Advanced
satsilemsatsilem
4

hopper

Plan the smallest shippable unit and first action under 30 minutes.

Community
Intermediate
intersystems-communityintersystems-community
27

objectscript-debugging

Diagnose IRIS runtime and compile errors using diagnostic packets and source mapping.

Official
Advanced
shirulotshirulot

gh-fix-ci

Diagnose failing GitHub Actions CI checks by fetching logs and extracting failure patterns.

Community
Intermediate