Migrate or align frontend repositories to the stock Vite+ workflow. Use when standardizing package or monorepo repos around `vp`, `voidzero-dev/setup-vp`, `vite-plus/test`, and Vite+ native CI, test, packaging, and hook flows, including Vite+ 0.2.x Vitest-wrapper cleanup.
70
94%
Does it follow best practices?
Impact
46%
0.92xAverage score across 6 eval scenarios
Passed
No known issues
{
"context": "Tests whether the agent migrates test imports from direct vitest to vite-plus/test, updates test scripts correctly, avoids invented commands, and handles coverage migration in a coordinated way.",
"type": "weighted_checklist",
"checklist": [
{
"name": "vite-plus/test imports",
"description": "Updated test files import from `vite-plus/test` instead of directly from `vitest` (e.g. `import { describe, it, expect } from 'vite-plus/test'`)",
"max_score": 20
},
{
"name": "vp test in scripts",
"description": "The `test` script in package.json is updated to use `vp test` (not `vitest run`, not `pnpm exec vitest`)",
"max_score": 15
},
{
"name": "No invented vp subcommands",
"description": "The output does NOT contain invented commands such as `vp vitest`, `vp exec vitest`, or `vp run vitest`",
"max_score": 15
},
{
"name": "Watch script uses vp test watch",
"description": "The watch-mode test script (if present) uses `vp test watch` (the documented subcommand) and not `vp test --watch`, raw `vitest`, or any direct vitest invocation",
"max_score": 10
},
{
"name": "Coverage script uses vp test run --coverage",
"description": "The coverage script (if present) uses `vp test run --coverage` (the documented subcommand form for one-shot coverage runs) rather than `vp test --coverage` or a direct vitest coverage invocation",
"max_score": 10
},
{
"name": "Coverage migrated together",
"description": "Coverage configuration and test-command wiring are updated in the same set of changes as the test script migration (both appear in the output artifacts)",
"max_score": 10
},
{
"name": "No direct package manager test call",
"description": "The output does NOT recommend running tests via `pnpm test`, `npm test`, or `yarn test` in updated scripts or documentation",
"max_score": 10
},
{
"name": "Coverage dependency kept aligned",
"description": "If coverage uses `@vitest/coverage-v8`, the output keeps it on the same upstream Vitest version bundled by the installed Vite+ release and avoids introducing duplicate Vitest versions",
"max_score": 10
}
]
}