subwave-worktree-dev

Prepare a Subway git worktree with env files and mirrored state for dev stack startup.

1.2k|104|Updated May 11, 2026
One-click install
npx skills add https://github.com/perminder-klair/subwave --skill subwave-worktree-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subwave-worktree-dev
Source: https://github.com/perminder-klair/subwave/tree/main/.claude/skills/subwave-worktree-dev
Command: npx skills add https://github.com/perminder-klair/subwave --skill subwave-worktree-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git, lsof, ps, docker compose, curl, npm, and includes scripts (resource) components.

What problem does it solve?

This Skill fixes the common problem where testing a different git branch in a worktree fails in dev mode because critical gitignored files (env files and precomputed state) are missing, even though the tracked source is present.

Core Features & Use Cases

  • Stages a git worktree for dev runtime by copying required env files and mirroring the operator’s declarative station state from the main checkout.
  • Safely prepares station readiness by scaffolding missing runtime prerequisites (like liquidsoap playlists and required state files) without copying container-generated runtime artifacts that would conflict.
  • Starts the full dev stack from the worktree by running the bundled prep script, then bringing up containers and launching the web dev server.

Quick Start

Tell the AI: "Prep my current git worktree for Subwave dev mode and start the stack from it."

Frequently Asked Questions about subwave-worktree-dev

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

FAQPage Schema
How do I run a docker compose dev stack from a git worktree without missing env files?

To run a docker compose dev stack from a git worktree, you must scaffold missing gitignored env files and mirror required state from the main checkout before starting containers. This ensures the linked worktree has the necessary runtime prerequisites.

Why does testing a branch in a git worktree fail in dev mode?

Testing a branch in a git worktree often fails in dev mode because critical gitignored files, such as environment configurations and precomputed station state, are missing from the new worktree directory despite the tracked source code being present.

What is the best way to mirror station state into a new git worktree?

The best way to mirror station state into a git worktree is to copy required state settings, moods, sfx, jingles, sessions, and voice files from the main checkout, deliberately excluding container-generated runtime artifacts to prevent file conflicts.

Does running the web npm dev server require an npm install in the worktree?

Running the web npm dev server can require an npm install in the worktree, which can be triggered optionally during the environment preparation phase before bringing up the docker compose stack with the --build flag.

Can I reset station state when scaffolding a worktree for dev mode?

You can optionally reset station state when scaffolding a worktree for dev mode, alongside staging root, controller, web, and docker env files to safely prepare runtime prerequisites without impacting the main checkout's state.

What dependencies do I need to prepare a git worktree for dev mode?

To prepare a git worktree for dev mode, you need bash, git, lsof, ps, docker compose, curl, and npm installed and accessible in your environment to execute the scaffolding scripts and start the full stack.