worktree-stack

Name: worktree-stack
Availability: InStock
Author: LanternOps

Provision isolated Breeze stacks with pg, Redis, API, web, portal, and Caddy per git worktree.

73|23|Updated Jan 14, 2026

Search Tags:#devops #orchestration #worktree #playwright #end-to-end-testing #breeze-stack

Ready to run

npx skills add https://github.com/LanternOps/breeze --skill worktree-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-stack
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/worktree-stack
Command: npx skills add https://github.com/LanternOps/breeze --skill worktree-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provision isolated, seeded Breeze stacks for the active git worktree to enable reliable end-to-end testing without cross-worktree interference.

Core Features & Use Cases

Isolated per-worktree stacks running pg, Redis, API, web, portal, and Caddy for the worktree's own code.
Emits a JSON descriptor with baseUrl, apiUrl, portalUrl, and admin credentials for automated testing and validation.
Drives Playwright-based testing workflows against the stack and supports up/down lifecycle commands.

Quick Start

Start the per-worktree Breeze stack and run Playwright tests against the generated base, api, and portal URLs.

Frequently Asked Questions about worktree-stack

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

FAQPage Schema

How do I run isolated end-to-end tests for each git worktree?▼

Provisioning isolated, seeded Breeze stacks for each git worktree enables reliable end-to-end testing without cross-worktree interference. Each stack runs pg, Redis, API, web, portal, and Caddy for the worktree's own code.

Can I use Playwright for end-to-end testing against a per-worktree stack?▼

Yes, Playwright-driven testing workflows are supported against the per-worktree stack. The skill emits a JSON descriptor with baseUrl, apiUrl, portalUrl, and admin credentials to drive automated Playwright tests.

How do I get the API and portal URLs for automated testing in a Breeze stack?▼

The Breeze stack emits a JSON environment descriptor containing baseUrl, apiUrl, portalUrl, and admin credentials. Automated testing and validation frameworks consume this descriptor to target the correct endpoints.

What services are included in a per-worktree Breeze stack orchestration?▼

A per-worktree Breeze stack orchestrates pg, Redis, API, web, portal, and Caddy services. These services run isolated to the worktree's code to prevent testing interference across concurrent worktrees.

Does the Breeze stack lifecycle support shared mode for testing?▼

Yes, the Breeze stack supports up/down lifecycle commands alongside an optional shared mode. This allows flexible stack orchestration for testing or demos depending on isolation requirements.

Do I need to manually seed the database for end-to-end testing in each worktree?▼

No, the Breeze stack provisions seeded stacks automatically for the active git worktree. This eliminates manual database seeding and ensures consistent end-to-end testing environments.