new-spawn

Automate GitHub repository setup, code pushes, and webhook configuration for VPS deployment.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/kdrezo/claude-skills --skill new-spawn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-spawn
Source: https://github.com/kdrezo/claude-skills/tree/main/new-spawn
Command: npx skills add https://github.com/kdrezo/claude-skills --skill new-spawn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning the current project into a spawn-based deployment on a VPS, coordinating GitHub setup, pushing code, configuring webhooks, and validating deployment.

Core Features & Use Cases

  • Automates repository creation or usage of an existing GitHub repo, pushes the current project, and wires a spawn deployment to a VPS.
  • Configures GitHub webhooks to trigger deployments on push and manages per-branch containers and subdomains.
  • Use Case: You want a new feature branch to instantly deploy to a dedicated container and subdomain on your VPS for testing.

Quick Start

Run the workflow to transform the current directory into a deployable spawn project and verify deployment on the VPS.

Frequently Asked Questions about new-spawn

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

FAQPage Schema
How do I automate deploying to a VPS via GitHub webhooks?

Automating VPS deploys via GitHub webhooks involves configuring a repository to trigger deployments on push. This skill coordinates repository creation, code pushing, webhook configuration, and initial deployment verification automatically.

Can I deploy a new feature branch to a dedicated container on my VPS?

Yes, deploying a new feature branch to a dedicated container is supported. The automation configures per-branch containers and subdomains on your VPS, allowing isolated testing environments to be deployed instantly when you push code.

Do I need an existing GitHub repository to set up automatic VPS deployment?

No, an existing GitHub repository is not required. The workflow can automate the creation of a new GitHub repository or use an existing one, then wires the spawn deployment to your VPS and configures the necessary webhooks.

What is the best way to trigger deployments across multiple VPS instances?

Triggering deployments across multiple VPS instances is best handled by configuring GitHub webhooks to manage per-branch containers. This approach automates subdomain routing and validates initial deployment triggering across the instances.

Does this deployment automation check for SSH access before pushing code?

Yes, SSH access checks are performed before pushing code. The automation satisfies requirements for verifying SSH access to the VPS, ensuring secure connections are established before repository creation and webhook configuration proceed.

Why use Docker containers for per-branch VPS deployments?

Using Docker containers for per-branch VPS deployments provides isolated testing environments with dedicated subdomains. This approach ensures feature branches deploy instantly without interfering with the main application or other active branches.