codebuddy-deploy

Orchestrate zero-downtime deployments with PM2 cluster mode and rollback.

2|1|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/lpding888/aiygw4.0 --skill codebuddy-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebuddy-deploy
Source: https://github.com/lpding888/aiygw4.0/tree/main/skills/codebuddy_deploy_skill
Command: npx skills add https://github.com/lpding888/aiygw4.0 --skill codebuddy-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe, zero-downtime deployment with rapid rollback capabilities, ensuring online services remain available during releases.

Core Features & Use Cases

  • Deployment orchestration: packaging, uploading, extracting, installing dependencies, building, and reloading with PM2 in cluster mode.
  • Safety gates: reviewer and QA gating, health checks, and post-release smoke tests to prevent faulty releases.
  • Observability and rollback: quick rollback to previous versions and centralized monitoring of health, performance, and logs.

Quick Start

To deploy, generate a build, upload to the server, install dependencies, start the process manager, run health checks, switch the current symlink, and perform post-release smoke tests.

Frequently Asked Questions about codebuddy-deploy

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

FAQPage Schema
How do I achieve zero-downtime deployment with PM2 in cluster mode?

Zero-downtime deployment with PM2 is achieved by packaging builds, uploading to servers, extracting, installing dependencies, and reloading processes in cluster mode. This orchestrates release workflows across server clusters while maintaining continuous online service availability.

What is the best way to ensure rapid rollback during a faulty release?

Rapid rollback during a faulty release is best handled by switching the current symlink to the previous version after health checks fail. This enables quick rollback to previous versions within a 3-minute window, ensuring immediate service recovery.

Does Nginx support health checks and post-release smoke testing for safe deployment?

Nginx supports safe deployment workflows when integrated with reviewer and QA gating, health checks, and post-release smoke tests. This combination prevents faulty releases by validating service health and performance before completing traffic routing.

Can I use QA gating and environment isolation for server cluster releases?

QA gating and environment isolation are fully supported for server cluster releases. This approach ensures that only reviewed and tested builds pass safety gates, satisfying environment separation and observability through centralized logs and monitoring.

How does observability through logs and monitoring work during a zero-downtime deployment?

Observability during zero-downtime deployment works by centralizing health, performance, and log monitoring across server clusters. This provides real-time visibility into the release process, enabling rapid detection and quick rollback of faulty versions within 3 minutes.

What are the limitations of manual rollback without a QA gating deployment workflow?

Manual rollback without a QA gating deployment workflow lacks automated health checks and post-release smoke tests, increasing the risk of extended downtime. Without centralized observability and symlink switching, rollback exceeds the 3-minute target and compromises service availability.