deployment

Automate deployment orchestration with PM2 and persistent preview URLs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nera0875/BUILDER --skill deployment-nera0875
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/nera0875/BUILDER/tree/main/.claude/skills/deployment
Command: npx skills add https://github.com/nera0875/BUILDER --skill deployment-nera0875

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pm2, jq.

What problem does it solve?

This Skill automates the deployment of built projects, ensuring stable preview URLs, robust process management with PM2, and consistent configuration. It eliminates manual deployment errors, guarantees project uptime, and provides a reliable, bookmarkable access point for every project.

Core Features & Use Cases

  • Persistent Port Assignment: Assigns a unique, stable port to each project that never changes, ensuring consistent preview URLs even after redeployments.
  • PM2 Process Management: Installs PM2, creates production-ready ecosystem.config.js, and manages project processes with auto-restart, memory limits, and centralized logging.
  • Automated Health Checks: Systematically verifies that the deployed application is running and responding with HTTP 200 OK, ensuring successful startup.
  • Build Validation: Critically ensures a fresh production build, preventing common 404 errors from development builds by cleaning and rebuilding automatically.
  • Use Case: After a successful build and testing, simply ask the AI "Deploy my project" and it will handle port assignment, PM2 setup, health checks, and provide a stable preview URL.

Quick Start

Deploy the current project and provide a preview URL.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I deploy a built project with a persistent preview URL?

Deployment automates port assignment, PM2 process management, and health checks to provide a stable, unchanging preview URL for your project. Each deployment maintains the same port and URL, ensuring consistent access across redeployments.

How does PM2 manage deployed applications?

PM2 handles process management by creating an ecosystem.config.js file, enabling auto-restart on failures, enforcing memory limits, and centralizing logs. This ensures production-ready uptime and monitoring for deployed projects.

Can I automate deployment after a successful build and tests?

Yes, deployment runs after builds and E2E validation complete, automatically handling port assignment, PM2 setup, and health verification. It ensures a fresh production build and validates the application responds with HTTP 200 before provisioning the preview URL.

What does the deployment health check verify?

Health checks systematically confirm the deployed application is running and responding with HTTP 200 OK, validating successful startup and preventing common 404 errors from incomplete or development builds.

Does deployment work with both frontend and backend projects?

Yes, deployment handles both frontend and backend deployments with identical persistent port assignment, PM2 management, and health monitoring, supporting heterogeneous project stacks in a single orchestration.

What happens if a deployed process fails?

PM2 automatically restarts failed processes and maintains centralized logs, ensuring recovery without manual intervention. Memory limits prevent resource exhaustion, keeping deployments stable across restarts.