AI Blocks › Ship and host your app
Ship a new version and prove visitors see the new build
Give it your project. Get a version, changelog, go or no-go call and proof it is live.
Release a new version and prove it is live is a free AI workflow for the job "Ship and host your app". It guides your AI through several skills in order, passing each step's output to the next.
Free · No account · Made by AI Blocks
What it does
A deploy that says "success" does not mean visitors see your change. A cache, a wrong branch or a build that failed quietly can leave the old version up. Teams find out when a customer reports the bug they already fixed. A release also goes out with a version nobody chose and notes nobody wrote. The steps put a check at each point. First it sets the version and writes the changelog from your commits. You review, merge and tag. Then it runs a go or no-go check and lists blockers. You fix them. Only then does it deploy to Vercel. Last it compares what the live site serves with the release you tagged, and says shipped only when they match.
You give it
- Your project (a folder or repo with its git history and tags)
- Your Vercel account, signed in on your computer
- Your build and test commands (optional)
You get
- A version number worked out from your commits, and a changelog grouped into added, changed and fixed
- A go or no-go call with each blocker listed
- A live link on Vercel
- A report that compares the live site with the release you tagged
Use it when
- You are releasing a new version and cannot afford a bad deploy.
- You have shipped, then found the old version still live.
- Your release notes and version numbers are guesses, not worked out from the commits.
Steps
- Release preparer: Point it at your project. Get the version bumped, a changelog written and a tagged release ready to publish.
- Ship readiness gate: Before you release. Get a go or no-go from set checks, with the blockers listed.
- Vercel publisher: Say "deploy my app". Get it live on Vercel as a preview or production site, with the link.
- Deploy verifier: Run it before you deploy. Get silent failure modes checked, then proof that the live version is the new one.
How to use it
- Download the handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
- Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
- Sign in to Vercel first. The deploy step asks for a preview first and production only after you agree.
- Do your two steps, which are to merge and tag, then to fix blockers.