worktree-flow

Coordinates Docker-isolated per-branch worktrees and PRs into dev.

1|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/emmepra/ora-et-labora --skill worktree-flow-emmepra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-flow
Source: https://github.com/emmepra/ora-et-labora/tree/main/skills/worktree-flow
Command: npx skills add https://github.com/emmepra/ora-et-labora --skill worktree-flow-emmepra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and coordinate the lifecycle of feature work in branches and per-branch worktrees, ensuring deterministic naming, isolated Docker runtime, and safe PR-to-dev integration.

Core Features & Use Cases

  • Deterministic worktree creation and naming per issue
  • One issue, one branch, one worktree, one PR flow into dev
  • Docker isolation across worktrees to prevent port and runtime conflicts Use cases include starting new work, resuming paused work, rebasing task branches, and opening update PRs to dev with validated state.

Quick Start

Create or resume the worktree for an active issue and open a draft PR to dev following the naming conventions.

Frequently Asked Questions about worktree-flow

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

FAQPage Schema
How do I isolate Docker runtime environments when working on multiple git branches?

Git worktrees isolate Docker runtime environments by creating branch-local directories with deterministic naming, preventing port and runtime conflicts across concurrent feature branches.

What is the best way to manage a one branch one PR workflow into dev?

Managing a one branch one PR workflow into dev involves coordinating per-issue worktree creation and applying deterministic branch lifecycles to safely open validated update PRs.

How do I prevent port conflicts across multiple local Docker service instances?

To prevent port conflicts across multiple local Docker service instances, you create isolated worktrees per branch, ensuring each feature environment operates independently without overlapping port assignments.

How do I resume paused work on a git feature branch with isolated state?

Resuming paused work on a git feature branch with isolated state requires restoring the branch-local .project state within its dedicated worktree to safely continue the PR flow.

Does worktree-flow require Docker to manage branch lifecycles?

Worktree-flow applies to projects using Docker, ports, and service orchestration where isolated environments and deterministic branch lifecycles are needed to prevent integration conflicts into dev.