verify-svelte-compat

Verifies rsvelte compiler output matches the official Svelte compiler across external repositories.

218|11|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/baseballyama/rsvelte --skill verify-svelte-compat-baseballyama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-svelte-compat
Source: https://github.com/baseballyama/rsvelte/tree/main/.claude/skills/verify-svelte-compat
Command: npx skills add https://github.com/baseballyama/rsvelte --skill verify-svelte-compat-baseballyama

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Porting the Svelte 5 compiler to Rust requires proof that rsvelte produces output equivalent to the official compiler on real-world codebases. Manually cloning external Svelte tools and apps, swapping in the Rust compiler, running their test suites, and diffing results is slow and error-prone. ## Core Features & Use Cases - Submodule-based target ingestion: Adds or updates external Svelte repositories as git submodules pinned to the latest stable tag, then classifies them as tool-type or app-type via automated usage analysis. - Compiler swap and dual-run verification: Builds the rsvelte NAPI binding, injects a Node.js loader that redirects svelte/compiler imports to rsvelte, and compares test results or per-file compiled output (canonicalized via OXC) against the official compiler baseline. - Automated regression fixing: On mismatch, creates a minimal reproduction in the pattern corpus, delegates a fix to an agent mirroring the official compiler implementation, validates with fmt/clippy/tests, and iterates until zero failures. - Use Case: Run /verify-svelte-compat https://github.com/sveltejs/kit to confirm rsvelte compiles every .svelte file in SvelteKit identically to the official compiler, automatically fixing any divergence on the rsvelte side. ## Quick Start Run /verify-svelte-compat with a GitHub URL or an existing submodule name to verify that repository against rsvelte.

Frequently Asked Questions about verify-svelte-compat

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

FAQPage Schema
How do I verify rsvelte compatibility with an external Svelte repository?▼

Run /verify-svelte-compat with a GitHub URL to add the repo as a submodule, or pass an existing submodule name to update and re-verify it. The skill builds the rsvelte NAPI binding, swaps the compiler, runs the target's tests, and diffs results against the official compiler baseline.

How does the skill test Svelte apps that do not import the compiler directly?▼

App-type targets are verified by compiling every .svelte file with both the official compiler and rsvelte in client and server modes, then comparing outputs through an OXC-based canonicalize_js binary. Semantic diffs, rsvelte errors, or canonicalize errors cause a non-zero exit.

Does verify-svelte-compat modify the target repository being tested?▼

No, fixes are applied only to the rsvelte side; the target repo is treated as the official-compatibility reference. Any package.json overrides injected during verification are reverted in the mandatory cleanup step before committing.

What happens when a compatibility regression is found?▼

A minimal reproduction is added to the pattern corpus, an agent mirrors the official Svelte compiler implementation to fix rsvelte, and the fix is validated with cargo fmt, clippy, and the release test suite. The verify-fix loop repeats up to five iterations before asking the user.

What are the prerequisites for running this Svelte compatibility verification?▼

You need cargo, pnpm, Node.js 22 or later, git, and an initialized submodules/svelte checkout. The compatibility/verify-svelte-compat directory is gitignored, so submodule additions require the -f flag.