AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Pages Push Vite

skill-stuffbucket-skills-pages-push-vite · by stuffbucket

Pushes the current branch to the git remote, triggering the GitHub Actions workflow that builds and deploys the Vite project to GitHub Pages. Guards that the remote exists and the workflow file is committed before pushing. USE FOR: the push step in the Pages deployment pipeline after prepare → build → commit.

↗ Website ↗ Repository
— No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-stuffbucket-skills-pages-push-vite

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Pages Push Vite? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

pages-push-vite

Push the committed changes to the remote, triggering the GitHub Actions Pages deployment.

When to Use

  • After pages-commit-vite has committed the workflow and vite config
  • Ready to trigger the CI deploy for the first time or after reconfiguration

Pipeline Position

pages-prepare-vite  →  pages-build-vite  →  pages-commit-vite  →  [pages-push-vite]  →  pages-publish-vite

What This Skill Does

  1. Resolves the remote name (default: origin) and current branch
  2. Guards: verifies the remote is configured
  3. Guards: verifies .github/workflows/deploy.yml is tracked by git (committed)
  4. Runs git push

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

  1. GitHub Actions triggers the Deploy to GitHub Pages workflow
  2. The build job runs npm ci + npm run build → uploads dist/ as a Pages artifact
  3. The deploy job deploys the artifact to Pages
  4. 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools