Skip to content

docs: jj workspaces live inside the repo under .workspaces - #20

Open
runewright[bot] wants to merge 1 commit into
mainfrom
change/worktree-rule
Open

docs: jj workspaces live inside the repo under .workspaces#20
runewright[bot] wants to merge 1 commit into
mainfrom
change/worktree-rule

Conversation

@runewright

@runewright runewright Bot commented Aug 4, 2026

Copy link
Copy Markdown

The JujutsuToolkit skill places parallel-work workspaces inside the repository under .workspaces/<name>.

Plan

The skill's workspace guidance matches the GitWorktrees rule: in-repo .workspaces/<name>, not sibling directories, so agents and humans find and clean them the same way.

Changes

  • JujutsuToolkit skill skills/JujutsuToolkit/SKILL.md: workspace creation examples and guidance use .workspaces/<name> inside the repository.

Testing

  • Push-gate prek checks green

Note

Update jj workspace path guidance to use .workspaces/<name> inside the repo

Updates SKILL.md to recommend placing workspaces under .workspaces/<name> inside the repo rather than as sibling directories (e.g., ../repo-<name>). The new guidance explains that .workspaces/ is covered by .gitignore and that sibling directories can pollute the parent directory and break IDE workspace paths.

📊 Macroscope summarized f268d9e. 1 file reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

@runewright
runewright Bot requested a review from N4M3Z as a code owner August 4, 2026 09:36
## Parallel agents

Multiple agents editing one working copy still collide at the file level; jj only removes the index collision. Give each agent its own working copy sharing one store: `jj workspace add ../repo-agent-1` creates an isolated directory and `@` backed by the same history and op log. This is the jj-native replacement for the git-worktree lifecycle (no manual create / rebase / remove / delete-branch). Companions: `jj workspace list`, `jj workspace forget`.
Multiple agents editing one working copy still collide at the file level; jj only removes the index collision. Give each agent its own working copy sharing one store: `jj workspace add .workspaces/agent-1` creates an isolated directory and `@` backed by the same history and op log. Workspaces live in `.workspaces/<name>` inside the repo, ignored by `.gitignore`; sibling directories (`../repo-<name>`) pollute the parent directory and break IDE workspace paths. This is the jj-native replacement for the git-worktree lifecycle (no manual create / rebase / remove / delete-branch). Companions: `jj workspace list`, `jj workspace forget`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 High JujutsuToolkit/SKILL.md:35

The guidance states that .workspaces/<name> is ignored by .gitignore, but the repository's .gitignore has no .workspaces/ entry — it only ignores .worktrees/. Running jj workspace add .workspaces/agent-1 therefore creates a nested working copy that is not excluded from the outer workspace, so the parent @ can snapshot the inner workspace's files and contaminate the parent change with unrelated agent edits. Either add .workspaces/ to .gitignore before recommending this layout, or remove the claim that the directory is already ignored.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
In file @skills/JujutsuToolkit/SKILL.md around line 35:

The guidance states that `.workspaces/<name>` is ignored by `.gitignore`, but the repository's `.gitignore` has no `.workspaces/` entry — it only ignores `.worktrees/`. Running `jj workspace add .workspaces/agent-1` therefore creates a nested working copy that is not excluded from the outer workspace, so the parent `@` can snapshot the inner workspace's files and contaminate the parent change with unrelated agent edits. Either add `.workspaces/` to `.gitignore` before recommending this layout, or remove the claim that the directory is already ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants