Resolves the remote name (default: origin) and current branch
Guards: verifies the remote is configured
Guards: verifies .github/workflows/deploy.yml is tracked by git (committed)
Runs git push <remote> <branch>
After push, GitHub Actions picks up the push event and starts the Deploy to GitHub Pages workflow.
How to Use
# Push current branch to origin
bash skills/pages-push-vite/scripts/push_pages.sh
# Push to a different remote or branch
bash skills/pages-push-vite/scripts/push_pages.sh upstream
bash skills/pages-push-vite/scripts/push_pages.sh origin feature/my-branch
Arguments
Position
Default
Description
$1
origin
Remote name
$2
current branch
Branch to push
What Happens After Push
GitHub Actions triggers the Deploy to GitHub Pages workflow
The build job runs npm ci + npm run build → uploads dist/ as a Pages artifact
The deploy job deploys the artifact to Pages
Use pages-publish-vite to monitor the run and get the live URL
Guidelines
Run from the project root
Confirm pages-commit-vite has run and the commit exists locally before pushing
For first-time push to a new remote, you may need to set upstream: git push -u origin main
(edit the script or run manually if the guard fails)
Force-push (--force) is intentionally not supported here
1---2name: pages-push-vite3description: pages-push-vite4---56# pages-push-vite78Push the committed changes to the remote, triggering the GitHub Actions Pages deployment.910## When to Use1112- After `pages-commit-vite` has committed the workflow and vite config13- Ready to trigger the CI deploy for the first time or after reconfiguration1415## Pipeline Position1617```text18pages-prepare-vite → pages-build-vite → pages-commit-vite → [pages-push-vite] → pages-publish-vite19```2021## What This Skill Does22231. Resolves the remote name (default: `origin`) and current branch242. Guards: verifies the remote is configured253. Guards: verifies `.github/workflows/deploy.yml` is tracked by git (committed)264. Runs `git push <remote> <branch>`2728After push, GitHub Actions picks up the `push` event and starts the `Deploy to GitHub Pages` workflow.2930## How to Use3132```bash33# Push current branch to origin34bash skills/pages-push-vite/scripts/push_pages.sh3536# Push to a different remote or branch37bash skills/pages-push-vite/scripts/push_pages.sh upstream38bash skills/pages-push-vite/scripts/push_pages.sh origin feature/my-branch39```4041## Arguments4243| Position | Default | Description |44| ---------- | --------- | ------------- |45| `$1` | `origin` | Remote name |46| `$2` | current branch | Branch to push |4748## What Happens After Push49501. GitHub Actions triggers the `Deploy to GitHub Pages` workflow512. The `build` job runs `npm ci` + `npm run build` → uploads `dist/` as a Pages artifact523. The `deploy` job deploys the artifact to Pages534. Use `pages-publish-vite` to monitor the run and get the live URL5455## Guidelines5657- Run from the project root58- Confirm `pages-commit-vite` has run and the commit exists locally before pushing59- For first-time push to a new remote, you may need to set upstream: `git push -u origin main`60 (edit the script or run manually if the guard fails)61- Force-push (`--force`) is intentionally not supported here
Run npx skillmds@latest add stuffbucket/pages-push-vite in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
pages-push-vite It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
stuffbucket (@stuffbucket) published this skill. Their other Agent Skills are listed on their SkillMD profile.
stuffbucket