How to Deploy a Vibe-Coded App to GitHub Pages Using AI (6 Prompts, Zero Manual Setup)
Learn how to deploy a vibe-coded project to GitHub Pages using just 6 AI prompts — from local folder to live URL, including CI/CD and a GitHub Pages intro site.
You’ve finished vibe-coding something. It actually works. Now what?
Most people stall here. They know they need to push to GitHub, set up CI/CD, and somehow get a public URL — but suddenly it feels like real work again. The vibe is gone.
Here’s what I figured out after running a few open source projects end-to-end with AI doing all the DevOps: there are exactly 6 prompts that take you from a local folder to a live GitHub Pages site with auto-build releases. I’ve tested this across multiple projects and the flow holds.
What You Need Before You Start
A GitHub account and a repo already created (empty is fine)
Claude Code or any AI coding assistant running in your project folder
Your project in a local directory — working or not, doesn’t matter yet
That’s it. No terminal mastery required. The AI handles git, GitHub Actions, and gh-pages config for you.
The 6-Prompt Flow
Prompt 1 — Start development inside your project folder
Open [your project folder] and start building [brief description].
This gets the AI oriented in the right directory. It begins scaffolding, naming files, and writing the first working version.
Prompt 2 — Checkpoint: commit and keep going
Git commit the current progress, then continue building.
After each working milestone, use this. The AI will write a commit message, stage everything, and commit. Version control happens automatically — you never have to think about it.
Prompt 3 — Push to your GitHub repo
Push this project to [your GitHub repo URL].
The AI runs git remote add origin, sets the upstream, and pushes. If there’s a conflict or SSH key issue, it’ll flag it. Usually it just works.
Prompt 4 — Set up CI/CD with auto-release
Set up GitHub Actions so that when I tag a release, it auto-builds the exe and creates a GitHub Release with the built file attached.
This creates a .github/workflows/release.yml that triggers on tags. Useful if you’re building desktop tools or CLIs. For web projects, adjust the build step to match your stack (Vite, Next.js, plain HTML, etc.).
Prompt 5 — Create your first release
Release this as v1.0.0.
The AI creates and pushes a git tag. The GitHub Action triggers. Within a minute or two, your first release is live with the built artifact attached.
Prompt 6 — Generate and deploy a GitHub Pages intro site
Look at [this GitHub Pages example URL], then create a GitHub Pages intro site for this project and deploy it.
Provide a reference site you like the style of. The AI generates a clean index.html (or React/Vite if you prefer), pushes to gh-pages branch, and enables Pages in the workflow. You get a free public URL at yourusername.github.io/your-repo.
Gotchas
GitHub Actions permissions: The default GITHUB_TOKEN may not have write access to create releases. If it fails, go to Repo → Settings → Actions → General → Workflow permissions and set it to “Read and write permissions.”
gh-pages branch doesn’t exist yet: On first deploy, the Action needs to create the branch. If it errors, add fetch-depth: 0 to your checkout step so it has full git history.
Windows exe build: If you’re building a .exe with PyInstaller or similar, the runner must be windows-latest, not ubuntu-latest. Specify this in the workflow matrix.
GitHub Pages source: After the Action deploys, you still need to go to Repo → Settings → Pages → Source → Deploy from branch → gh-pages. The AI doesn’t always do this automatically.
What You End Up With
Full git history from day one
Auto-release pipeline triggered by a single tag
A public-facing GitHub Pages site with your project intro
Zero manual
gitcommands after setup
The whole flow takes about 20–30 minutes the first time. On subsequent projects, it’s faster because you can reuse the workflow files.
I’ve run this on four projects so far. The bottleneck is always the GitHub Actions permissions step — everything else the AI gets right on first try.
What’s Next
If you found this useful, the next step is setting up auto-tagging so releases happen on every merge to main — not just when you remember to tag. I’ll cover that in an upcoming paid post with the full workflow YAML template.
FAQ
Q: Does this work with Claude Code specifically, or any AI coding assistant?
A: The 6 prompts are tool-agnostic. I’ve tested them with Claude Code (CLI) and they work the same in Cursor or GitHub Copilot Chat. The key is running the AI inside your project directory so it can read and write files directly.
Q: What if my project is a Python script, not a web app — can I still use GitHub Pages?
A: GitHub Pages hosts static HTML/CSS/JS only. For a Python project, Prompt 6 generates an HTML landing page about your project (screenshots, install instructions, download links). The Python script itself gets distributed via the GitHub Release from Prompt 4/5.
Q: How do I push to GitHub if I’ve never set up SSH keys?
A: Tell the AI: “Help me set up SSH key authentication for GitHub on this machine.” It’ll walk you through ssh-keygen, adding the key to your GitHub account, and testing the connection. Takes about 5 minutes once.
Q: Is GitHub Pages actually free? Any limits I should know about?
A: Yes, free for public repos. Limits: 1 GB storage, 100 GB bandwidth/month, builds limited to 10 per hour. For most personal projects and open source tools, you’ll never hit these. If you’re expecting high traffic, pair it with a CDN or move to Cloudflare Pages (also free).
Q: What’s the difference between this flow and just using git push manually?
A: The manual approach means you’re also writing the GitHub Actions YAML, debugging workflow syntax, figuring out artifact paths, and setting up Pages manually. This flow offloads all of that to the AI. You get CI/CD and a public site in the same session as building the project — before you lose momentum.
Q: Can I use this for a private repo?
A: GitHub Pages requires a public repo on the free plan. For private repos you need GitHub Pro ($4/month). Alternatively, deploy the Pages site to a separate public repo while keeping the source code private — the AI can set that up too with Prompt 6.
Q: What happens to my GitHub Pages site if I delete the gh-pages branch?
A: The site goes offline immediately. The branch is the source. Keep it, or if you reorganise, re-enable Pages under Settings → Pages after pushing to the new branch.