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.
94
94%
Does it follow best practices?
Impact
95%
2.63xAverage score across 3 eval scenarios
Passed
No known issues
{
"context": "Tests whether the agent correctly migrates GitHub Actions CI to the VitePlus-native setup, using the right setup action and install commands, while preserving release steps and using vp run for repo-specific scripts.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses setup-vp action",
"description": "The migrated workflow uses `voidzero-dev/setup-vp@v1` instead of a hand-rolled `actions/setup-node` or Corepack bootstrapping step",
"max_score": 15
},
{
"name": "Includes vp env step",
"description": "The CI workflow includes a `vp env` step as part of the setup sequence",
"max_score": 10
},
{
"name": "Uses vp install",
"description": "The workflow uses `vp install` to install dependencies instead of `pnpm install`, `npm install`, or `yarn install`",
"max_score": 10
},
{
"name": "Uses vp check and vp test",
"description": "The workflow runs `vp check` and `vp test` (or `vp check && vp test`) for verification, not direct vitest or eslint invocations",
"max_score": 10
},
{
"name": "vp run for custom scripts",
"description": "Any repo-specific scripts not replaced by VitePlus built-ins are invoked via `vp run <script>` rather than `pnpm run` or `npm run`",
"max_score": 10
},
{
"name": "No direct package manager commands",
"description": "The migrated CI file does NOT contain `pnpm`, `npm`, or `yarn` used directly as install/run commands (e.g. no `pnpm install`, `npm ci`, `yarn install`)",
"max_score": 10
},
{
"name": "Release steps preserved",
"description": "The npm publish, GitHub Release, or other release/publish steps from the original workflow are preserved and NOT deleted",
"max_score": 15
},
{
"name": "Release workflow file retained",
"description": "The release workflow file (e.g. release.yml) is kept in the output with its release-specific steps intact",
"max_score": 10
},
{
"name": "Output includes workflow files",
"description": "At least one updated GitHub Actions YAML workflow file is present in the output",
"max_score": 10
}
]
}