fix-errors

Trace VS Code telemetry data flow to identify and fix unhandled errors.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/darwinboaventura/base-vscode-copilot --skill fix-errors-darwinboaventura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/darwinboaventura/base-vscode-copilot/tree/main/.github/skills/fix-errors
Command: npx skills add https://github.com/darwinboaventura/base-vscode-copilot --skill fix-errors-darwinboaventura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unhandled errors surfaced by the VS Code error telemetry dashboard can obscure root causes and slow remediation. This Skill provides a structured approach to diagnosing, enriching context, and correcting telemetry-related failures.

Core Features & Use Cases

  • Guided error reasoning: Traces data flow from error producers to consumers to identify root causes without masking problems.
  • Telemetry enrichment: Preserves diagnostic context in error messages to aid faster triage and resolution.
  • Best-practice fixes: Encourages fixing at the data producer or validation boundary rather than at symptoms.

Quick Start

Provide a concrete failing telemetry incident and obtain a concise fix plan.

Frequently Asked Questions about fix-errors

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

FAQPage Schema
How do I diagnose unhandled VS Code telemetry errors from a stack trace?

Diagnose unhandled telemetry errors by tracing data flow from error producers to consumers to identify the root cause without masking the problem. This guided approach distinguishes data sources to pinpoint exact failure origins.

What is the best way to enrich error messages with diagnostic context for faster triage?

Preserve diagnostic context within telemetry failure logs to aid faster triage and resolution. This enrichment ensures that production-safe changes to data handling retain enough context to prevent recurrence.

How do I fix telemetry failures at the source instead of masking the symptoms?

Apply fixes at the data producer or validation boundary rather than at the symptoms. Correcting telemetry failures at the source ensures that production-safe changes prevent the unhandled error from recurring.

Does this diagnostic approach work for any VS Code telemetry incident?

This diagnostic approach works for any VS Code telemetry incident where you can provide a concrete failing telemetry incident. It then guides you to trace data flow and validate fixes at the source.

Why do unhandled errors in the VS Code error telemetry dashboard obscure root causes?

Unhandled errors in the VS Code error telemetry dashboard obscure root causes because they lack sufficient diagnostic context, slowing remediation. Enriching error messages and tracing data flow resolves this ambiguity.