mock-to-internals-migration

What problem does it solve?

Migrating test mocks from Vitest to Bun's native test runner introduces common pitfalls like broken test isolation, missing real module exports in mocks, and broken barrel import patterns that can silently break test suites and introduce flaky test behavior.

Core Features & Use Cases

• Strict Procedural Guardrails: Defines required pre- and post-migration steps including baseline test runs, barrel export audits, and mock spread validation to prevent common migration errors.
• Forbidden Shortcut Prohibitions: Explicitly bans risky practices like inventing custom gating mechanisms or dismissing post-change test failures as pre-existing without verification.
• Validation Checklists: Provides dedicated reviewer and test engineer checks to verify command transformation idempotency, mock correctness, and test suite integrity after migration.
• Use Case: Ideal for development teams moving their test infrastructure from Vitest to Bun, ensuring mock conversions preserve existing test coverage and behavior without regressions.

Quick Start

Use the mock-to-internals-migration skill to convert all Vitest mock calls in your project's test suite to compatible Bun internal mock patterns while maintaining full test integrity.