open

Creates an isolated git worktree workspace with its own branch and namespaced runtime for one job.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/fallguyconsulting/ok-plugins --skill open-fallguyconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open
Source: https://github.com/fallguyconsulting/ok-plugins/tree/main/plugins/ok/families/ok-workspaces/skills/open
Command: npx skills add https://github.com/fallguyconsulting/ok-plugins --skill open-fallguyconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Parallel development jobs collide when they share one checkout: branches tangle, local environment files conflict, and runtime stacks fight over the same ports. This Skill gives each job its own worktree, branch, and runtime namespace so concurrent work stays isolated inside the project. ## Core Features & Use Cases - Worktree-per-job isolation: Creates a git worktree on its own branch using the committed profile's naming conventions (worktrees.dirPrefix, worktrees.branchPrefix), defaulting to .ok-workspaces/worktrees/<job> inside the project. - Ephemeral config carry-over: Copies gitignored local files (.env, .env.*, .claude/settings.local.json) from the main checkout into the new worktree. - Namespaced runtime provisioning: For docker-compose it sets COMPOSE_PROJECT_NAME and re-allocates pinned host ports; for dev-server it allocates a port block via the materialized allocator script. - Use Case: You need to fix a bug while a feature branch is mid-review. Run /open bugfix-login to get a separate worktree on branch wt/bugfix-login with its own compose project and ports, leaving your current checkout untouched. ## Quick Start Ask the assistant to open a workspace for a job, for example: open a workspace for the login bugfix job.

Frequently Asked Questions about open

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

FAQPage Schema
How do I create an isolated git worktree for a new job?▼

Invoke the /open slash command with a kebab-case job slug. It runs git worktree add using the profile's dirPrefix and branchPrefix, copies gitignored env files, and provisions the runtime namespace for that job.

How do I run multiple docker-compose stacks from one repository?▼

Give each job its own worktree and set a unique COMPOSE_PROJECT_NAME per workspace. This Skill appends the namespaced project name to the worktree's .env and re-allocates any pinned host ports to free ones.

What happens if the worktree directory or branch already exists?▼

The Skill stops and reports the conflict instead of reusing or clobbering the existing workspace. You must resolve the collision manually or choose a different job slug before retrying.

Does git worktree carry over my local .env files?▼

No, git worktree only checks out tracked files. This Skill copies untracked local-env files such as .env, .env.*, and .claude/settings.local.json from the main checkout into the new worktree and lists what it copied.

When should I not use worktree-per-job isolation?▼

Avoid it when the job depends on uncommitted changes in your current checkout, since the Skill stops rather than moving work between trees. It also requires a committed .ok-workspaces/config.json profile, so run /ok first if none exists.