ios-worktree

Create and manage isolated jj workspaces for iOS tasks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nclandrei/dotfiles --skill ios-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-worktree
Source: https://github.com/nclandrei/dotfiles/tree/main/config/skills/ios-worktree
Command: npx skills add https://github.com/nclandrei/dotfiles --skill ios-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage isolated jj workspaces for iOS tasks.

Core Features & Use Cases

  • Isolated iOS task workspaces within a single repository to prevent cross-task contamination of dependencies and configurations.
  • Lifecycle commands: new, list, open, clean, and clean --all to create, view, and manage workspaces with safety checks (e.g., never removing the default workspace).
  • Environment hygiene: copies root .env* files when present and ensures .workspaces/ is properly gitignored to maintain clean repo state.

Quick Start

Create a new ios-workspace named my-ios-task to start an isolated iOS development session.

Frequently Asked Questions about ios-worktree

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

FAQPage Schema
How do I create isolated iOS workspaces within a single repository?

To create isolated iOS workspaces, use the new command to generate a dedicated jj workspace. This separates tasks from the main workspace, preventing cross-task contamination of dependencies and configurations.

What is the best way to manage multiple iOS tasks in the same jj repository?

Managing multiple iOS tasks in a jj repository is best handled by creating isolated workspaces. This approach ensures clean naming, separate worktrees, and safe environment preservation for each task.

How does workspace isolation prevent cross-task contamination in iOS development?

Workspace isolation prevents cross-task contamination by keeping each iOS task in a separate jj workspace. This guarantees that dependencies and configurations for one task do not interfere with another.

Can I safely clean up all jj workspaces without removing the default workspace?

Yes, you can safely clean up workspaces using the clean or clean --all commands. These lifecycle commands include safety checks that explicitly prevent the removal of the default workspace.

Does creating an isolated jj workspace copy environment files automatically?

Yes, creating an isolated jj workspace automatically copies root .env* files when present. It also ensures the .workspaces/ directory is properly gitignored to maintain a clean repository state.

What lifecycle commands are available for managing jj workspaces?

The available lifecycle commands for managing jj workspaces include new, list, open, clean, and clean --all. These commands allow you to create, view, access, and safely remove workspaces.