fix-errors

Trace telemetry data flow to identify and fix unhandled errors.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill fix-errors-devflex-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/DevFlex-AI/devonz-editor-web/tree/main/.github/skills/fix-errors
Command: npx skills add https://github.com/DevFlex-AI/devonz-editor-web --skill fix-errors-devflex-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unhandled errors reported by telemetry dashboards can obscure the true source of the problem. This Skill provides a structured approach to tracing the data flow, identifying the producer of invalid data, and enriching error messages to aid diagnostics without masking the original failure.

Core Features & Use Cases

  • Error-telemetry analysis: Trace data from the point of emission through the stack to identify the producer of invalid data and surface actionable diagnostics.
  • Safe remediation patterns: Emphasize fixes that preserve visibility in telemetry and avoid silencing errors at the crash site.
  • Scope across processes: Guides apply when data traverses IPC, extension APIs, or worker threads in complex applications.

Quick Start

Follow these guidelines to begin diagnosing a telemetry error by tracing data flow and enriching diagnostic context.

Frequently Asked Questions about fix-errors

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

FAQPage Schema
How do I trace unhandled errors in telemetry dashboards back to their source?

Trace unhandled telemetry errors by following the data flow from the point of emission through the stack trace to identify the producer of invalid data and surface actionable diagnostic context.

What is the best way to debug telemetry errors that traverse IPC channels in large JavaScript projects?

Debug telemetry errors across IPC channels and extension APIs by tracing data flow across processes, validating data producers, and enriching error messages to preserve diagnostic visibility without masking the original failure.

How do I fix telemetry error handling without silencing the original crash site?

Fix telemetry error handling by applying safe remediation patterns that enrich diagnostic context and avoid silencing errors at the crash site, ensuring visibility is preserved throughout the telemetry pipeline.

Can I use this diagnostic approach for stack traces with hit counts and affected users in TypeScript projects?

Yes, this diagnostic approach applies to large JavaScript and TypeScript projects, analyzing stack traces, hit counts, and affected users to identify invalid data producers and enforce best practices for telemetry pipelines.

Why do my telemetry dashboards show unhandled errors with no clear source?

Unhandled telemetry errors obscure their true source when data producers emit invalid data across IPC channels or extension APIs, requiring a structured data flow trace to surface the underlying failure and provide diagnostic context.

What are the limitations of silencing errors at the crash site in telemetry pipelines?

Silencing errors at the crash site masks the original failure and reduces visibility in telemetry dashboards, making it harder to validate data producers and trace the root cause of unhandled errors across processes.