fix-errors

Trace data flow through call stacks to diagnose unhandled VS Code telemetry errors.

189k|41.5k|Updated Sep 3, 2015
One-click install
npx skills add https://github.com/microsoft/vscode --skill fix-errors-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-errors
Source: https://github.com/microsoft/vscode/tree/main/.github/skills/fix-errors
Command: npx skills add https://github.com/microsoft/vscode --skill fix-errors-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to investigating and resolving unhandled errors reported through VS Code's error telemetry, ensuring robust error management.

Core Features & Use Cases

  • Root Cause Analysis: Guides users to trace errors back to their origin, rather than just fixing the symptom.
  • Data Flow Tracing: Emphasizes understanding data flow through call stacks to identify data producers.
  • Enriched Error Reporting: Provides strategies for adding diagnostic context to error messages for better telemetry.
  • Use Case: When a new error appears in the telemetry dashboard with a stack trace, use this Skill to systematically debug it by following the data upstream to its source.

Quick Start

Use the fix-errors skill to trace the data flow for an unhandled error reported in telemetry.

Frequently Asked Questions about fix-errors

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

FAQPage Schema
How do I debug unhandled errors reported in VS Code telemetry?

Debugging VS Code telemetry errors involves tracing data flow through call stacks to identify the data producer, rather than just patching the crash site, ensuring the root cause is resolved.

What is the best way to find the root cause of an error call stack?

Finding the root cause of an error call stack requires tracing the data upstream to its source. This approach focuses on identifying the data producer instead of merely fixing the immediate crash symptom.

How do I add diagnostic context to error messages for better telemetry?

You can enrich error messages by adding diagnostic context when the data producer cannot be immediately identified, providing better telemetry for future troubleshooting and root cause analysis.

Why should I trace data flow upstream instead of fixing errors at the crash site?

Tracing data flow upstream is recommended because fixing errors at the crash site only addresses the symptom. Following the data to its producer ensures you resolve the actual root cause of the unhandled error.

Can I use this approach for any unhandled VS Code error with a stack trace?

Yes, when a new error appears in the telemetry dashboard with a stack trace, you can systematically debug it by following the data upstream to its source to identify the root cause.