deploy-prod

Commit, push, monitor CI, and deploy Vue and Astro production builds.

4|2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/gparker97/beanies-family --skill deploy-prod-gparker97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-prod
Source: https://github.com/gparker97/beanies-family/tree/main/.claude/skills/deploy-prod
Command: npx skills add https://github.com/gparker97/beanies-family --skill deploy-prod-gparker97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and safeguards the end-to-end process of committing changes, pushing to main, monitoring CI and security workflows, and deploying the Vue and Astro production sites so releases are consistent, auditable, and require explicit user confirmation.

Core Features & Use Cases

  • Commit & Push Safety: Review pending changes, draft and confirm commit messages, enforce pre-push tests, and push without using --no-verify or force options.
  • Change Classification: Diff against the last successful workflow SHAs to determine whether the Vue PWA, Astro marketing site, both, or neither need deployment.
  • CI & Deploy Orchestration: Monitor main CI and security workflows, limit retry attempts for fixes, trigger deploy workflows only after explicit user approval, and summarize deployment results.
  • Use Case: When a change touches shared packages and src/, use this Skill to ensure both apps are identified, CI/security gates pass, and deployments are executed in the correct order.

Quick Start

Use the deploy-prod skill to stage and commit changes, push to main, monitor CI and security runs, and deploy the affected production sites after confirming each step.

Frequently Asked Questions about deploy-prod

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

FAQPage Schema
How do I safely deploy a Vue PWA and Astro site to production using GitHub Actions?

Deploy a Vue PWA and Astro site by committing changes, pushing to main, and monitoring GitHub Actions CI workflows. The process diffs against the last successful SHAs to classify changes, enforces pre-push tests, and requires explicit user confirmation before triggering production deploy workflows.

What is the best way to automate CI validation before a production deploy?

CI validation before production deploy is automated by monitoring main CI and security workflows on GitHub. The process limits retry attempts for failed fixes, gates deployment until workflows pass, and summarizes deployment results for auditable releases.

Do I need GitHub CLI authenticated to deploy production builds?

Yes, GitHub CLI must be authenticated as gparker97 to deploy production builds. The deployment process relies on the CLI to monitor GitHub Actions workflows and trigger the deploy.yml and deploy-web.yml workflows after CI and security gates pass.

How does change classification work for monorepo deployments with shared packages?

Change classification for monorepo deployments works by diffing current code against the last successful workflow SHAs. This determines whether the Vue PWA, Astro marketing site, both, or neither require deployment when changes touch shared package or application source code.

Can I use --no-verify or force push when deploying production updates?

No, you cannot use --no-verify or force push options when deploying production updates. The process enforces pre-push tests and requires safe commits to maintain release consistency and auditability across the Vue and Astro production sites.

What happens if CI pipelines fail during a production deployment?

If CI pipelines fail during production deployment, the process limits retry attempts for fixes and halts the deployment. It requires CI and security gates to pass before allowing explicit user confirmation to trigger the production deploy workflows.