cabloy-worktree-environment

Configures deterministic Vona and Zova local environment files for linked Cabloy Git worktrees.

971|132|Updated Jan 14, 2018
One-click install
npx skills add https://github.com/cabloy/cabloy --skill cabloy-worktree-environment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cabloy-worktree-environment
Source: https://github.com/cabloy/cabloy/tree/main/.claude/skills/cabloy-worktree-environment
Command: npx skills add https://github.com/cabloy/cabloy --skill cabloy-worktree-environment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running multiple Cabloy checkouts in parallel causes port collisions and shared identity conflicts between Vona backend and Zova frontend runtimes. This Skill generates a deterministic, secret-safe local environment for a linked Git worktree without ever reading existing .env file contents.

Core Features & Use Cases

  • Worktree Validation: Verifies the current checkout is a linked (not primary) Cabloy Basic or Cabloy Start worktree using Git metadata before any write.
  • Deterministic Port Generation: Derives SERVER_LISTEN_PORT, DEV_SERVER_PORT, and DEV_SERVER_HMR_PORT from fixed baselines plus a worktree ordinal and batch offset, with a "Try another batch" flow for collisions.
  • Secret-Safe Writes: Writes only new or empty vona/env/.env.local and zova/env/.env.local files after git check-ignore verification and explicit user confirmation, never reading existing env content.
  • Use Case: A developer creates a second linked worktree to run a feature branch alongside the main checkout, invokes the skill, confirms the proposed port tuple, and gets isolated local overrides ready for npm run dev.

Quick Start

Invoke /cabloy-worktree-environment inside a linked Cabloy worktree and confirm the proposed identity and port tuple to write the local environment files.

Frequently Asked Questions about cabloy-worktree-environment

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

FAQPage Schema
How do I run multiple Cabloy worktrees without port conflicts?

Invoke this skill inside each linked Git worktree to generate deterministic local overrides. It assigns ports by adding the worktree ordinal to fixed baselines (7102, 9000, 24679), so each worktree gets a distinct SERVER_LISTEN_PORT, DEV_SERVER_PORT, and HMR port.

How to set up Vona and Zova environment files in a Git worktree?

The skill writes vona/env/.env.local and zova/env/.env.local with a shared APP_NAME from the worktree basename, a Vona listen port, and an API_BASE_URL pointing at that port. Both files are written only after git check-ignore verification and your explicit confirmation.

Can I use this skill in the primary Cabloy checkout?

No. The skill compares git-dir and git-common-dir and rejects the primary checkout, since equal paths identify it. It only operates in registered linked worktrees detected via git worktree list.

What happens if my .env.local files already contain credentials?

The skill never reads, parses, or displays any .env file content. If a target file exists and is non-empty, it stops without modifying either file, and you must manage that file manually or use a fresh linked worktree.

What if the proposed ports are already in use?

Say "Try another batch" and the skill increments the batch offset, advancing every recommended port by exactly one and regenerating API_BASE_URL. Nothing is written during a batch change, and the proposal is not a live port reservation.

Does the generated environment isolate databases and external services?

A unique APP_NAME separates framework-managed test database names and Redis prefixes only. Explicitly named databases, custom Redis keys, mail, payment, webhooks, and object storage remain shared and require a separate isolation design.