vscode-extension-debugger

Debug and fix VS Code extension runtime errors, memory leaks, and WebView issues.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/retz8/iris --skill vscode-extension-debugger-retz8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vscode-extension-debugger
Source: https://github.com/retz8/iris/tree/main/.claude/skills/vscode-extension-debugger
Command: npx skills add https://github.com/retz8/iris --skill vscode-extension-debugger-retz8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill equips developers with a structured approach to diagnosing and fixing bugs in VS Code extensions, reducing time spent on guesswork and unproductive debugging.

Core Features & Use Cases

  • Guided debugging workflows: triage, root-cause analysis, fix implementation, and verification.
  • Comprehensive coverage: handles runtime errors, memory leaks, WebView issues, activation problems, and extension communication challenges.
  • Practical examples: reproduce a failure, apply proven patterns, and validate fixes with unit and integration tests.

Quick Start

Use this skill to guide debugging a failing extension, outlining a reproducible scenario and a step-by-step plan for triage, root-cause analysis, and verification.

Frequently Asked Questions about vscode-extension-debugger

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

FAQPage Schema
How do I debug a VS Code extension activation failure?

Debug VS Code extension activation failures using a structured triage workflow that isolates root causes, applies safe fixes, and verifies results with unit and integration tests.

What is the best way to fix memory leaks in VS Code extensions?

Fix memory leaks in VS Code extensions through guided root-cause analysis and proven debugging patterns, ensuring stable runtime behavior across the extension lifecycle.

How do I troubleshoot WebView communication issues in a VS Code extension?

Troubleshoot WebView communication issues by following a structured debugging workflow that diagnoses extension communication challenges and validates fixes with integration tests.

Can I use a structured workflow to debug runtime errors across the VS Code extension lifecycle?

Yes, you can debug runtime errors across the VS Code extension lifecycle using a guided workflow covering triage, root-cause analysis, fix implementation, and verification.

Why does my VS Code extension fail to communicate properly during runtime?

VS Code extension communication failures require root-cause analysis to diagnose, applying structured debugging workflows to identify the failure point and implement a safe fix.