一键导入
deploy-coolify-review-env
// Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.
// Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.
Write workflow harness files that define role, status semantics, feedback loops, and durable delivery rules for disposable ticket workspaces.
Clarify ambiguous requests with a focused, Socratic interview before planning or implementation.
Review behavior, risk, performance, and test coverage before style nits.
Review trust boundaries, auth, input handling, secrets, and dependency risk before release.
Turn a clarified spec into milestone-oriented tickets, dependency edges, and stage-gated delivery lanes.
Platform operations for tickets, projects, and runtime coordination inside OpenASE.
| name | deploy-coolify-review-env |
| description | Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast. |
Set these environment variables either in the skill-local .env file or on the
agent machine / provider runtime:
COOLIFY_BASE_URLCOOLIFY_API_TOKENCOOLIFY_PROJECT_UUIDCOOLIFY_SERVER_UUIDCOOLIFY_DESTINATION_UUIDCOOLIFY_GIT_REPOSITORYCOOLIFY_PORTS_EXPOSESCOOLIFY_ENVIRONMENT_NAMECOOLIFY_TEMPLATE_APPLICATION_UUIDSet COOLIFY_REPOSITORY_MODE to one of:
public (default)private-github-appprivate-deploy-keyIf COOLIFY_REPOSITORY_MODE=private-github-app, also set:
COOLIFY_GITHUB_APP_UUIDIf COOLIFY_REPOSITORY_MODE=private-deploy-key, also set:
COOLIFY_PRIVATE_KEY_UUIDCOOLIFY_BUILD_PACK (default dockerfile)COOLIFY_BASE_DIRECTORYCOOLIFY_PUBLISH_DIRECTORYCOOLIFY_DOCKERFILE_LOCATIONCOOLIFY_INSTALL_COMMANDCOOLIFY_BUILD_COMMANDCOOLIFY_START_COMMANDCOOLIFY_HEALTH_CHECK_ENABLEDCOOLIFY_HEALTH_CHECK_PATHCOOLIFY_HEALTH_CHECK_PORTCOOLIFY_AUTOGENERATE_DOMAINCOOLIFY_DOMAIN_TEMPLATE where {{name}} becomes the generated app nameCOOLIFY_DESCRIPTION_PREFIX (default OpenASE review env)COOLIFY_ENV_PREFIX (default review)COOLIFY_NAME_MAX_LENGTH (default 48).codex/skills/deploy-coolify-review-env/.env
when the skill is injected into a runtime..env..env.example, then fill the real secrets into .env.COOLIFY_ENVIRONMENT_NAME is set, the scripts always deploy into that
fixed Coolify environment.review-<slugged-branch>--env-name or --app-name if needed.This skill is currently wired for:
My first projectreviewopenase-mainhttp://{{name}}.100.90.170.69.sslip.ioApplication names still remain branch-scoped so each review deployment gets its own temporary application under the same environment.
Deploy or update a review environment:
.codex/skills/deploy-coolify-review-env/scripts/deploy_review_env.sh --branch feature/my-change
Delete the same review environment:
.codex/skills/deploy-coolify-review-env/scripts/delete_review_env.sh --branch feature/my-change
Delete a ticket-scoped app from the shared review environment by ticket id:
.codex/skills/deploy-coolify-review-env/scripts/delete_review_env.sh --env-name review --ticket-identifier ASE-623
codex-config.toml / codex wrapper mountsreview environment wiring, ticket cleanup targets the
matching application and skips deleting the shared environment itself.--wait-seconds on deploy when a workflow should wait for a terminal
deployment state before moving a ticket to human review.