jj-workspace-experiments

Create isolated jj workspaces for parallel experiments and shared repository history.

11|1|Updated Apr 9, 2025
One-click install
npx skills add https://github.com/thoughtpolice/a --skill jj-workspace-experiments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jj-workspace-experiments
Source: https://github.com/thoughtpolice/a/tree/main/.claude/skills/jj-workspace-experiments
Command: npx skills add https://github.com/thoughtpolice/a --skill jj-workspace-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create isolated jj workspaces to test changes, run experiments in parallel, and explore alternative implementations without impacting the main workspace.

Core Features & Use Cases

  • Create dedicated workspaces for each experimental path to avoid cross-contamination.
  • Run long-running builds/tests in parallel across multiple workspaces without blocking others.
  • Compare results between approaches using shared history and separate work trees.

Quick Start

Create an isolated experiment workspace using jj workspace add --name=<experiment-name> work/<directory-name> to start testing changes.

Frequently Asked Questions about jj-workspace-experiments

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

FAQPage Schema
How do I create isolated jj workspaces to run parallel experiments?

To create isolated jj workspaces for parallel experiments, use the command jj workspace add --name=<experiment-name> work/<directory-name> to generate a separate work tree sharing repository history.

What is the best way to test breaking changes without affecting the main workspace?

Testing breaking changes without affecting the main workspace involves creating dedicated jj workspaces to isolate modifications, preventing cross-contamination while evaluating alternative implementations using shared history.

Can I run long-running builds and tests in parallel using jj workspaces?

You can run long-running builds and tests in parallel across multiple jj workspaces, allowing concurrent operations to execute without blocking other workflows in the main repository.

How do I compare different implementation approaches using isolated workspaces?

Comparing implementation approaches using isolated workspaces involves creating separate work trees for each path, allowing you to evaluate results side-by-side while leveraging the shared repository history.

What happens to jj workspaces after finishing an experiment?

After finishing an experiment, jj workspaces can be forgotten or merged back, allowing you to clean up isolated work trees while preserving the shared repository history established during testing.