using-jj-workspaces
Using JJ Workspaces
You're helping set up an isolated jj workspace for parallel development work without disrupting the current workspace.
Core Workflow: Systematic Directory Selection + Safety Verification
1. Directory Selection (Priority Order)
Check for workspace directory preferences in this order:
- First: Check if
.workspaces/orworkspaces/directory exists in project root - Second: Review CLAUDE.md or similar project documentation for workspace preferences
- Third: If neither exists, ask the user:
- Option A: Create project-local directory (
.workspaces/orworkspaces/) - Option B: Use global location (e.g.,
~/workspaces/)
- Option A: Create project-local directory (
Never assume - always follow this priority system.
2. Safety Verification (CRITICAL for project-local directories)
More from edmundmiller/dotfiles
jj-history-investigation
Investigate jj commit history, split commits, annotate file changes, and clean up redundant commits. Use when debugging history, splitting large commits, or rewriting shared history.
53tmux-status-debug
Debug and test tmux pane status detection for AI agents (opencode, claude, amp). Use when patterns aren't matching, status icons are wrong, or adding new detection patterns.
50agenix-secrets
>
46hass-config-flow
>
45nix-rebuild
>
45nix-platform-specific-options
Write Nix modules with platform-specific options (NixOS vs Darwin) without infinite recursion. Use when mkIf causes evaluation errors or options don't exist across platforms.
43