#359
fix(deploy-to-vercel, vercel-cli-with-tokens): wait with `inspect --wait` instead of polling
Problem
After a deploy, both skills give agents a way to check status but no way to wait:
- The git-push flow says
sleep 5and then take the latest entry ofvercel ls --format json. If the deployment isn't registered yet, the latest entry is an older deployment, and agents retry with moresleeps. - The
--no-waitflows only offer a one-shotvercel inspect <url>. When the user wants the build result, agents end up insleep+vercel inspectloops, which waste turns and run for an unpredictable time.
Change
- Git push: find the pushed commit's deployment directly:
vercel ls <project-name> --meta githubCommitSha=$(git rev-parse HEAD) --format json→.deployments[0].url. The skill notes that it can take a few seconds to appear, and gives the GitLab and Bitbucket keys (gitlabCommitSha,bitbucketCommitSha). - Waiting: wherever the skills say "check status with
vercel inspect <url>", they now also give the blocking form:vercel inspect <url> --wait --timeout 20m. It returns when the build finishes and exits 1 onERROR,CANCELEDor timeout. The default--timeoutis 3m, which is too short for most real builds, so the skill recommends a longer one. On failure, read the logs withvercel inspect <url> --logs. --no-waitstays, so the URL still comes back fast.skills/deploy-to-vercel.zipandskills/vercel-cli-with-tokens.zipare rebuilt to match.
Verification
- Checked the flags in
vercel inspect --helpandvercel ls --helpon CLI 65.8.0 (--wait,--timeout,--logs,--meta). - Checked the exit codes in the CLI source:
timedOut ? 1 : exitCode(readyState), whereexitCodereturns 1 forERROR/CANCELED. - Ran
vercel ls <project> --meta githubCommitSha=<sha> --format jsonon a real GitHub-connected project. It returned exactly that commit's deployment. - Ran
vercel inspect <url> --wait --timeout 20mon a real deployment. It blocked until the build was READY. node scripts/build-discovery-index.mjs https://example.com/skillspasses (9 skills).
🤖 Generated with Claude Code
@SignorCrypto is attempting to deploy a commit to the Vercel Team on Vercel.
A member of the Team first needs to authorize it.