publish-site

Deploy static sites to GitHub Pages, Cloudflare Pages, or Netlify with versioned rollback.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill publish-site-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-site
Source: https://github.com/loteiron/ZeusAgent/tree/main/optional-skills/web-development/publish-site
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill publish-site-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting a locally built website, dashboard, or prototype onto a public URL involves juggling provider CLIs, build outputs, and DNS quirks, and a bad deploy can be hard to undo. This Skill standardizes the whole pipeline: local preview for sign-off, git-tagged versioning before every deploy, a provider fallback ladder, live HTTP verification, and one-command rollback. ## Core Features & Use Cases - Provider ladder deployment: Publishes static output to GitHub Pages by default, falling back to Cloudflare Pages or Netlify based on authenticated CLIs and user needs like custom domains. - Version-before-deploy discipline: Commits and tags every deploy (deploy-YYYYMMDD-HHMM) so any previous version can be restored by checking out a tag and redeploying. - Preview and verification workflow: Serves builds locally or via a cloudflared tunnel for sign-off, then confirms the live URL returns HTTP 200 with expected content before reporting success. - Use Case: You just generated a Vite-based analytics dashboard. Run the build, preview dist/ locally, tag the commit, push to GitHub Pages, and receive a verified live URL plus a rollback tag. ## Quick Start Publish the static site in my current project directory to GitHub Pages and give me the live URL.

Frequently Asked Questions about publish-site

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a static site to GitHub Pages from the command line?▼

Commit and tag your build output, then push the dist folder to a gh-pages branch with git subtree push and enable Pages via the gh api repos pages endpoint. The site appears at https://<owner>.github.io/<name>/ after a short build lag.

GitHub Pages vs Cloudflare Pages vs Netlify for static hosting?▼

GitHub Pages is the default when gh is authenticated since it needs no extra accounts. Cloudflare Pages adds custom domains, redirects, headers, and Functions via wrangler, while Netlify works as a fallback with draft deploy URLs for staging.

Why do my SPA routes return 404 on GitHub Pages?▼

GitHub Pages has no rewrite rules, so deep client-side routes 404. Copy index.html to 404.html in the output directory so routing recovers; Cloudflare Pages and Netlify handle this with a _redirects file containing /* /index.html 200.

How do I roll back a bad static site deploy?▼

Check out the previous deploy tag with git checkout deploy-<previous> and rerun the same deploy command. Cloudflare Pages and Netlify also keep per-deploy history in their dashboards with a rollback option.

Why do assets 404 after deploying a site that worked locally?▼

Pages hosts run case-sensitive Linux, so references like Logo.PNG fail if the committed file is logo.png. Project pages also serve under /<name>/, breaking absolute asset paths; use relative paths or set the build tool base.

Can I deploy a server-side app with this static hosting workflow?▼

No, this workflow covers only static sites and SPA build output, not server-side runtimes. For throwaway serverless deploys with zero account setup, use the cloudflare-temporary-deploy skill instead.