github-pages-deploy

Deploys static frontend builds to GitHub Pages and verifies the live site via curl-based checks.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill github-pages-deploy-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pages-deploy
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/web-dev/github-pages-deploy
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill github-pages-deploy-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Getting a frontend off localhost and onto a public URL often fails in non-obvious ways: git pushes hang over HTTPS, the deploy-pages action fails until a Pages source is enabled, and a successful build does not prove the deployed site is correct. This Skill walks through the full deployment and verifies the live artifact without needing a browser. ## Core Features & Use Cases - End-to-end deployment workflow: Build with npm/Vite, create the repo with the GitHub CLI, configure the SPA base path, and add a GitHub Actions workflow using actions/deploy-pages@v4. - Headless fixes for common failures: Switch to SSH when HTTPS pushes hang, and enable the Pages source via the GitHub REST API when the deploy job fails. - Browser-free verification: Fetch the deployed HTML and CSS with curl and grep for expected and forbidden structural signals using the included verify-deployed.sh script. - Use Case: You built a Vite + React dashboard and need to send a public link to a client, but browser automation is blocked. This Skill deploys it to https://you.github.io/repo/ and confirms the dashboard CSS is live and the old landing page is gone. ## Quick Start Deploy my built frontend to GitHub Pages and verify the live site contains the dashboard layout.

Frequently Asked Questions about github-pages-deploy

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

FAQPage Schema
How do I deploy a Vite app to GitHub Pages?▼

Build with npm run build, set base to "./" in vite.config.ts so assets resolve on the repo subpath, then add a GitHub Actions workflow using actions/upload-pages-artifact with path dist and actions/deploy-pages@v4. Push to main to trigger the deployment.

How to fix actions/deploy-pages failing with a 404 error?▼

The deploy job fails because the repository has no Pages source configured. Enable it headless by POSTing to the GitHub API repos/<you>/<repo>/pages endpoint with build_type set to workflow, then re-run the workflow with gh workflow run.

Why does git push to GitHub hang over HTTPS?▼

In some environments pushes to private repos stall silently over HTTPS while public repos work. The fix is switching to SSH: generate an ed25519 key, register it with gh ssh-key add (requires the admin:public_key scope), and set the remote to [email protected].

Can I verify a deployed website without opening a browser?▼

Yes, fetch the live HTML with curl, extract the hashed CSS asset path, download it, and grep for expected class names like .topbar and forbidden ones like .hero. This proves structure and content but not visual rendering, which still needs human review.

What are the limitations of curl-based deployment verification?▼

Grep checks on minified CSS confirm structural signals and content presence, not pixels. Shader, WebGL, and visual polish cannot be validated this way and require a human to inspect the live link.