Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/deploy-release-test
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch.
Passed 17 of 20 test cases with the skill, and 4 of 20 without it.
and 16 more in the full report
15 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which exact GitHub workflow file in vercel/next.js is dispatched for release deployment testing?
| Checked | Without skill | With skill |
|---|---|---|
| Dispatches workflow .github/workflows/test_e2e_deploy_release.yml | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill only when manually running the entire Next.js deployment test suite for a pull request. Treat package validation as a hard gate: never dispatch the workflow until the exact commit's redirected tarball responds successfully.
Do not use this workflow to sanity-check one deployment test or a focused group of tests. Follow Running Deploy Tests Locally instead:
NEXT_TEST_VERSION=https://vercel-packages.vercel.app/next/commits/<commit-sha>/next pnpm test-deploy <path-to-test>
If a request to "run deploy tests" does not explicitly call for the entire suite, prefer the focused local workflow and scope it to the affected tests.
vercel/next.js and workflow
.github/workflows/test_e2e_deploy_release.yml.vercel/next.js. A fork branch cannot
run this secret-bearing workflow; use the repository's PR adoption process
first when appropriate.Resolve the PR branch and its latest commit from GitHub, not merely from the local checkout:
gh pr view <pr-number> --repo vercel/next.js \
--json number,url,headRefName,headRefOid,isCrossRepository
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.