Migrate or align frontend repositories to the stock VitePlus workflow. Use when standardizing package or monorepo repos around `vp`, `voidzero-dev/setup-vp`, `vite-plus/test`, and VitePlus-native CI, test, and packaging flows, including updating scripts, test config, CI setup, and packaging commands.
98
100%
Does it follow best practices?
Impact
97%
1.73xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
{
"context": "Tests whether the agent correctly handles a VitePlus version upgrade by distinguishing between the global CLI upgrade surface and the project-local upgrade surface, explicitly updating the VitePlus core and test aliases that are NOT automatically re-resolved by a simple package update, and performing the correct end-to-end validation sequence.",
"type": "weighted_checklist",
"checklist": [
{
"name": "vp upgrade for global CLI",
"description": "The upgrade procedure includes `vp upgrade` to update the global `vp` binary on the machine — distinct from updating the project-local package",
"max_score": 12
},
{
"name": "Global before local",
"description": "The global `vp upgrade` step appears before (or is documented as separate from) the project-local `vp update` steps — the two surfaces are not conflated into a single operation",
"max_score": 8
},
{
"name": "vp update vite-plus",
"description": "The project-local update includes `vp update vite-plus` (updating the vite-plus package itself)",
"max_score": 10
},
{
"name": "Explicit core alias update",
"description": "The procedure explicitly updates `@voidzero-dev/vite-plus-core` with `vp update @voidzero-dev/vite-plus-core` (or combined with other packages) — NOT relying on `vp update vite-plus` alone to re-resolve this alias",
"max_score": 15
},
{
"name": "Explicit test alias update",
"description": "The procedure explicitly updates `@voidzero-dev/vite-plus-test` with `vp update @voidzero-dev/vite-plus-test` (or combined) — NOT relying on `vp update vite-plus` alone to re-resolve this alias",
"max_score": 15
},
{
"name": "vp outdated for verification",
"description": "The procedure uses `vp outdated` to confirm that all Vite+ packages are now at the intended release (not `npm outdated`, `pnpm outdated`, or omitted entirely)",
"max_score": 12
},
{
"name": "vp env current in validation",
"description": "The end-to-end validation sequence includes `vp env current` as the first check",
"max_score": 8
},
{
"name": "Full validation sequence",
"description": "The validation sequence includes all of: `vp install`, `vp check`, and `vp test` (in addition to `vp env current`)",
"max_score": 10
},
{
"name": "Build validation included",
"description": "The validation sequence includes `vp build` or `vp pack` (as appropriate for the project type) to verify build artifacts after the upgrade",
"max_score": 5
},
{
"name": "No direct package manager for VitePlus packages",
"description": "The upgrade steps do NOT use `npm install`, `pnpm update`, `yarn upgrade`, or other direct package-manager commands for the VitePlus packages — all updates go through `vp update`",
"max_score": 5
}
]
}