svelte/migration/cleanup

Removes migrated Svelte store files and verifies zero residual references before deletion.

6|6|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/intent-hq/cloudlands-fe --skill svelte-migration-cleanup-intent-hq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: svelte/migration/cleanup
Source: https://github.com/intent-hq/cloudlands-fe/tree/main/.agents/skills/themis/svelte/migration/cleanup
Command: npx skills add https://github.com/intent-hq/cloudlands-fe --skill svelte-migration-cleanup-intent-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After migrating a Svelte store to a Redux slice, leftover .store.svelte.ts files, stale imports, and hidden pass-through wrappers create dead code and regressions. This Skill provides a disciplined cleanup and rollback procedure so old stores are deleted only when it is safe. ## Core Features & Use Cases - Zero-Reference Verification: Runs targeted grep searches to confirm no consumer still imports the old store before deletion. - Pass-Through Wrapper Guard: Detects one-line re-exports, proxies, and delegate modules that keep old import paths alive, and requires documented sunset conditions for intentional compatibility shims. - Rollback Recipe: Restores the old store from git history, removes the new slice directory, reducer registration, and saga startup call when a migration must be reverted. - Use Case: After migrating a cart store to a Redux slice and passing tests, use this Skill to verify zero references, delete cart.store.svelte.ts, and produce a per-slice cleanup report. ## Quick Start Verify the migrated cart slice has zero remaining references to the old store, then delete the old .store.svelte.ts file and report the cleanup evidence.

Frequently Asked Questions about svelte/migration/cleanup

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

FAQPage Schema
How do I safely delete an old Svelte store after migration?▼

Delete the old .store.svelte.ts file only after tests and manual UI checks pass. Run grep searches like grep -rn "{old-store}.store" src/ to confirm zero references, then remove the file without leaving a barrel or re-export behind.

How to verify no references remain to a migrated Svelte store?▼

Run targeted searches such as grep -rn "{old-store}" src/ --include="*.ts" --include="*.svelte" and grep -rn "from.*stores/{old-store}" src/. Both must return no results before the old store file can be deleted.

How do I roll back a Svelte store to Redux migration?▼

Rollback restores the old store file and affected components from git history, removes the new slice directory, deletes the reducer constructor entry, and removes the matching store.runSaga startup call. Keep the old store in version control until verification completes.

What is a pass-through wrapper in a store migration?▼

A pass-through wrapper is a thin module that re-exports from the new path, such as export * from "new/path" or functions that only delegate to the new implementation. These must be removed or documented as compatibility shims with a sunset condition.

When should I keep a compatibility shim for an old store path?▼

Keep a shim only when an external consumer still imports the old path, such as a plugin awaiting its own migration. Document the consumer, the sunset or removal condition, and the new import path directly next to the shim.

Why should store migrations be limited to one store per commit?▼

Migrating one store per branch and per PR isolates regressions, makes rollback a simple git restore, and keeps review scope small. Batching multiple stores in one commit makes failures hard to attribute and revert.