VSCode Extension Resolver

Diagnose VSCode extension build failures in Nix configurations.

Updated Aug 23, 2026

Search Tags:#vscode #extension #nix #marketplace #build-fix

Ready to run

npx skills add https://github.com/Shavakan/nix-flakes --skill vscode-extension-resolver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: VSCode Extension Resolver
Source: https://github.com/Shavakan/nix-flakes/tree/main/.claude/skills/vscode-extension-resolver
Command: npx skills add https://github.com/Shavakan/nix-flakes --skill vscode-extension-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and fix VSCode extension build failures in Nix configurations by systematically testing sources across nixpkgs, vscode-marketplace, and open-vsx, reducing debugging time and guesswork.

Core Features & Use Cases

Systematic source testing: Test sources in priority order: nixpkgs curated, vscode-marketplace, and open-vsx.
Incremental testing strategy: Add one failing extension at a time to isolate the issue.
Guided fixes: Recommends source changes and updates to your nix configuration when a mismatch or missing extension is detected.

Quick Start

Provide the failing extension identifier (publisher.extension) and run the resolver to identify a reliable source; update your nix configuration accordingly.

Frequently Asked Questions about VSCode Extension Resolver

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

FAQPage Schema

How do I fix VSCode extension build failures in Nix configurations?▼

VSCode extension build failures in Nix occur when an extension source is unavailable or misconfigured. Test sources systematically across nixpkgs, vscode-marketplace, and open-vsx in priority order, adding one failing extension at a time to isolate the issue and identify a reliable source.

What causes VSCode extension hash mismatches or attribute-not-found errors in Nix?▼

Hash mismatches and attribute-not-found errors happen when an extension's source URL is stale, moved, or doesn't exist in the queried marketplace. The resolver catalogs these error types and recommends alternative sources from nixpkgs curated, vscode-marketplace, or open-vsx.

Can I use incremental testing to debug VSCode extension failures in Nix?▼

Yes. Incremental testing isolates failures by adding one extension at a time to your nix configuration, allowing you to identify which extension causes the build to fail and which source resolves it before updating modules/vscode/extensions.nix.

What's the best way to find a working VSCode extension source when the marketplace is unavailable?▼

Test multiple sources in order: nixpkgs curated extensions first, then vscode-marketplace, then open-vsx. The resolver systematically checks each source, handles marketplace 500 errors, and recommends the first working source for your extension identifier.

Do I need nix-vscode-extensions to use this resolver?▼

Yes. The resolver enforces function signatures that include nix-vscode-extensions and verifies it's present in your environment before diagnosing extension failures and updating your configuration.