render-pm2-clj-config

Render pm2-clj ecosystem files to JSON for validation and debugging.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill render-pm2-clj-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: render-pm2-clj-config
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/render-pm2-clj-config
Command: npx skills add https://github.com/open-hax/opencode-skills --skill render-pm2-clj-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Render pm2-clj ecosystem configuration files into JSON without starting any processes, helping validate structure and content safely.

Core Features & Use Cases

  • Render a single ecosystem file to JSON for inspection.
  • Validate the JSON structure and key fields without launching PM2.
  • Use this in debugging configurations after migrations or edits.

Quick Start

Run the render command with the path to ecosystem.pm2.clj to generate the JSON for quick verification.

Frequently Asked Questions about render-pm2-clj-config

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

FAQPage Schema
How do I validate a pm2-clj ecosystem config without starting processes?

You can validate a pm2-clj ecosystem config by rendering it to JSON without starting processes. This allows you to inspect the structure, verify app definitions, and check environment variables safely before deployment.

What is the best way to debug pm2-clj configuration files after a migration?

The best way to debug pm2-clj configurations after a migration is to render the ecosystem file to JSON. This outputs valid JSON for inspection and offers optional comparison to previous configurations to check parity.

Can I inspect pm2 environment variables in JSON format before launching PM2?

Yes, you can inspect environment variables by rendering the pm2-clj ecosystem file to JSON. This validation step outputs the configured environment variables in valid JSON format without launching the PM2 process manager.

Does rendering pm2-clj configs to JSON require a specific render command?

Rendering pm2-clj configs to JSON requires a clobber render command. You run this command with the path to your ecosystem configuration file to generate valid JSON output for verification.

Why does my pm2-clj config validation fail after editing the ecosystem file?

Config validation may fail after edits due to structural errors in the ecosystem file. Rendering the pm2-clj config to JSON helps identify these issues by validating the JSON structure and key fields without starting processes.