deploy-coolify-review-env

Create, update, and delete per-branch Coolify review environments via CLI.

264|27|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/PacificStudio/openase --skill deploy-coolify-review-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-coolify-review-env
Source: https://github.com/PacificStudio/openase/tree/main/.codex/skills/deploy-coolify-review-env
Command: npx skills add https://github.com/PacificStudio/openase --skill deploy-coolify-review-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python3, curl, and includes scripts (resource) components.

What problem does it solve?

Deploying per-branch preview environments and cleaning them up can be tedious and error-prone. This skill automates creating or updating a branch-scoped Coolify review environment and deleting it with a single, predictable command, helping teams review changes faster.

Core Features & Use Cases

  • Create or update a per-branch Coolify preview environment with a single command, using environment-driven configuration for portability and reuse.
  • Delete the same preview environment (and related apps) with a single command, enabling clean ticket cleanup.
  • Derive environment and application names from the branch by default, with optional overrides via environment variables for flexibility.

Quick Start

Use the deploy-coolify-review-env script to deploy a review environment for your feature branch by running with --branch <branch>.

Frequently Asked Questions about deploy-coolify-review-env

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

FAQPage Schema
How do I automate Coolify review environment creation for a feature branch?

You can automate Coolify review environment creation by running a single script command with the --branch flag. The skill automates creating or updating per-branch preview environments using environment-driven configuration for portability and reuse.

What is the best way to clean up Coolify preview environments after a ticket is closed?

The best way to clean up Coolify preview environments is using a single delete command that removes the branch-scoped environment and related apps, enabling clean ticket cleanup and preventing orphaned review deployments.

Do I need specific dependencies to run Coolify branch deployment scripts?

Yes, you need bash, python3, and curl installed to execute the Coolify branch deployment scripts. These dependencies support idempotent operations across environments and satisfy runtime configuration requirements.

Can I customize the environment name when deploying a Coolify review env?

Yes, you can customize the environment name when deploying a Coolify review env. The script derives environment and application names from the branch by default, but allows optional overrides via environment variables for flexibility.

How does deterministic environment naming work for ticket-driven Coolify workflows?

Deterministic environment naming for ticket-driven Coolify workflows works by deriving environment and application names directly from the branch name, ensuring consistent and predictable naming across environments with optional domain or env-name customization.