pm2-server-control

Start, stop, restart, delete, and monitor named PM2 processes.

3|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/viteinfinite/skills --skill pm2-server-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm2-server-control
Source: https://github.com/viteinfinite/skills/tree/main/skills/pm2-server-control
Command: npx skills add https://github.com/viteinfinite/skills --skill pm2-server-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting and stopping PM2 managed servers reliably without manual scripting saves time and reduces errors for local development and testing. PM2 lifecycle management should be repeatable across projects with clear process naming.

Core Features & Use Cases

  • Start and stop servers with a named process using the standard PM2 commands, enabling quick recovery from failures.
  • Inspect status, view logs, restart, or delete processes to maintain clean runtime environments.
  • Provides consistent process naming and safe cleanup to prevent orphaned processes across cycles.

Quick Start

Start your server with pm2 start ./my-server --name <name> --no-autorestart to bring it online.

Frequently Asked Questions about pm2-server-control

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

FAQPage Schema
How do I start a Node.js server with PM2 and prevent it from auto-restarting?

Start a PM2 managed server by running pm2 start ./my-server --name <name> --no-autorestart to bring it online with a consistent process name, enabling quick recovery from failures during local development and testing.

How do I view logs and inspect the status of PM2 managed processes?

View logs and inspect PM2 process status using pm2 logs and pm2 show commands, providing visibility into runtime environments and maintaining clean local development, testing, and staging workflows.

Can I use PM2 for process lifecycle management in staging and local development environments?

Yes, PM2 process lifecycle management is applicable to local development, testing, and staging workflows where named processes require reliable lifecycle management and visibility into status and logs.

What is the best way to clean up orphaned PM2 processes across restart cycles?

Clean up orphaned PM2 processes across cycles by using safe cleanup commands like pm2 delete alongside consistent process naming, preventing orphaned processes and maintaining clean runtime environments.

Why should I use consistent naming when starting and stopping PM2 servers?

Consistent naming when starting and stopping PM2 servers ensures repeatable lifecycle management across projects, preventing orphaned processes and enabling reliable status visibility and safe cleanup.