gk-svelte-effect-audit

To fix circular state updates in Svelte 5 $effect runes, scan your codebase for anti-patterns like state-update-in-effect and derived-via-effect, then apply safe edit-based auto-fixes and validate with pnpm check:fast.

Common $effect anti-patterns include circular-sync, derived-via-effect, state-update-in-effect, missing teardown, browser-guard redundancy, and logging-without-inspect, all of which cause inconsistent state and performance issues.

To audit $effect runes in a Svelte TypeScript codebase, scan src/.svelte and src/.ts files to pattern-match defined anti-patterns, classify findings by severity and confidence, and apply high-confidence auto-fixes.

Yes, you can automatically fix missing teardown and cleanup logic in $effect runes by running an audit that flags the missing cleanup anti-pattern and applies confident edit-based fixes followed by svelte autofixer validation.

Yes, the $effect rune audit works with $effect.pre and $effect.root usage by scanning Svelte component and TypeScript source files to identify risky patterns and apply severity-graded reporting with safe auto-fixes.

The best way to validate Svelte 5 $effect auto-fixes is to run pnpm check:fast and use the svelte autofixer tool on modified .svelte files, iterating subsequent autofix passes until the validation loop is clean.