hytaleservers-workflow

Automate HyTaleservers.tech development from git branches to VPS deployment.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/ragastar/hytaleservers --skill hytaleservers-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hytaleservers-workflow
Source: https://github.com/ragastar/hytaleservers/tree/main/.opencode/skills/hytaleservers-workflow
Command: npx skills add https://github.com/ragastar/hytaleservers --skill hytaleservers-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill standardizes and streamlines the HyTaleservers.tech development workflow, reducing miscommunication and manual steps from coding to deployment.

Core Features & Use Cases

  • Standardized development flow: feature branch creation, coding, local testing, commit, push, PR, and auto-deploy.
  • Clear project structure references and common commands for dev, build, deploy.
  • Use Case: A developer creates a feature, tests locally, then opens a PR; after merge → auto-deploy to VPS.

Quick Start

  • Create a feature branch: git checkout -b feature/your-feature
  • Make changes
  • Test locally: npm run dev (port 3000)
  • Commit: git commit -m "feat: your feature"
  • Push: git push origin feature/your-feature
  • Create PR on GitHub
  • After merge → auto-deploy to VPS (port 3003)

Frequently Asked Questions about hytaleservers-workflow

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

FAQPage Schema
How do I automate git workflow and deployment using GitHub Actions?

You can automate git workflow by creating feature branches, committing changes, and opening pull requests to trigger GitHub Actions for auto-deployment. This standardized pipeline enforces conventional commits and automates VPS deployment upon PR merge.

What is the standard development workflow for feature branch creation and auto-deploy?

The standard development workflow involves creating a git feature branch, testing locally via npm run dev, committing with conventional formats, pushing, and opening a PR. Merging the pull request automatically triggers deployment to the VPS.

How do I set up a pull request pipeline for automated VPS deployment?

Set up a pull request pipeline by using git branches for feature development and conventional commits for changes. Once a PR is merged, GitHub Actions automatically triggers a scripted pipeline to deploy the application to the VPS.

Does this automated deployment workflow require local testing before opening a pull request?

Yes, the workflow requires local testing before opening a pull request. Developers must run npm run dev on port 3000 to validate changes locally before pushing a feature branch and creating a PR for automated deployment.

What's the best way to standardize a development lifecycle from branching to deployment?

Standardize a development lifecycle by enforcing a scripted pipeline with git branches, conventional commits, and pull requests. This approach reduces manual steps and miscommunication, enabling contributors to collaborate, test, review, and push changes efficiently.

Why does my auto-deploy to VPS not trigger after a git commit?

Auto-deploy to VPS only triggers after a pull request is merged, not after a standard git commit. You must push your feature branch, create a PR, and ensure it is merged for the GitHub Actions deployment to execute.