Menu
Use when parallel isolation is needed — multiple agents/sessions working on the same jj repo, or when the user asks to work in a separate workspace without disturbing their current @.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user says "capture", or wants to remember, save, or note something for later.
Use when the user says "closeday", "close my day", or "end of day". End-of-day consolidation appended to today's Inbox note.
Use when the user says "today", "morning plan", "plan my day", "what should I work on", or asks about their priorities for the day.
Use whenever `jj root` succeeds. Use `jj` for all version-control operations; do not use `git`.
Use when the user asks to create a GitHub issue, file a bug, or track a task. Also use when the user describes a problem they found and wants to capture it.
Use when the user asks to open a PR, create a PR, or push and create a pull request.
| name | using-jj-workspaces |
| description | Use when parallel isolation is needed — multiple agents/sessions working on the same jj repo, or when the user asks to work in a separate workspace without disturbing their current @. |
Multiple working copies backed by a single repo. Each workspace has its own @ and directory on disk, but they share the same commit graph. Like git worktrees, but jj-native.
Opt-in, not default. Only use when parallel isolation is needed — don't create a workspace if you're the only session.
Use together with the using-jj skill. All normal jj rules still apply.
# Create — always pass -r so the base is explicit.
# Prefer -m so the new working-copy commit is clearly labeled.
jj workspace add ../ws-name -r 'trunk()' -m "description of work"
# Work in it — normal jj workflow applies
cd ../ws-name
# List all workspaces
jj workspace list
# Cleanup — forget first, then delete directory
jj workspace forget ws-name
rm -rf ../ws-name
When another session rewrites commits your @ depends on, your working copy goes stale. jj will warn you. Fix immediately:
jj workspace update-stale
Don't ignore stale warnings — working on stale state leads to confusing diffs and conflicts.
The orchestrating session creates the workspace, dispatches the agent into it, and is responsible for cleanup unless the agent is explicitly told to clean up.
jj workspace add ../ws-agent-task -r 'trunk()' -m "task: agent's work"
# dispatch agent with: "cd ../ws-agent-task and work there"
# after agent is done:
jj workspace forget ws-agent-task && rm -rf ../ws-agent-task