Agent skill · 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. Do not use for focused deployment-test sanity checks; run the relevant tests locally with pnpm test-deploy instead. Covers resolving the latest branch SHA, waiting for vercel-packages, preserving default workflow inputs, dispatching the workflow, and verifying the run.
What it needs
About 3k tokens when loaded.
What this skill does
Deploy Release Test 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. Scope Do not use this workflow to sanity-check one deployment test or a focused group of tests. Follow Running Deploy Tests Locally instead: 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. Inputs Accept a PR number or determine the PR from the current branch. Use repository vercel/next.js and workflow .github/workflows/teste2edeployrelease.yml. Require the PR head branch to exist in vercel/next.js. A fork branch cannot run this secret-bearing workflow; use the repository's PR adoption process first when appropriate. Workflow 1. Resolve the PR branch and its latest commit from GitHub, not merely from the local checkout: If no PR number was supplied, omit <pr-number> to detect the PR from the current branch. Stop if isCrossRepository is true. Record headRefName as the branch and headRefOid as the commit SHA. 2. Construct the exact package URL: 3. Wait for the package to become downloadable before dispatching anything: Keep the wait in an ongoing terminal session and poll it so the user still receives progress updates. The helper uses HEAD, follows the redirect to Vercel Blob, and only succeeds when the final artifact is available. Do not substitute a check that accepts the initial redirect: that endpoint can redirect even while the blob still returns 404. If the helper times out or reports an authorization or build failure, do not dispatch the workflow. Report the failure and inspect the commit's build-and-deploy / upload-preview-tarballs checks if useful. 4. Resolve the PR again immediately after validation. Compare the current headRefName and headRefOid with the recorded values. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/deploy-release-test