workspace

Create, list, open, and safely clean named jj workspaces under .workspaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

jj workspaces help teams isolate feature work and reviews, but managing multiple workspaces under .workspaces can be error-prone. This skill automates the lifecycle of named workspaces: creation, listing, opening, and safe cleanup, while protecting the default and current workspaces.

Core Features & Use Cases

  • Create new workspaces under .workspaces from a revision or the current checkout.
  • List all named workspaces, highlight the current one, and warn about finished or stale entries without auto-deleting them.
  • Open a named workspace by reporting its path and status so you can switch to it explicitly.
  • Clean a workspace with safety checks to avoid removing default or the active workspace, and confirm before deleting if there are unlanded changes.
  • Clean --all removes only finished task workspaces, skipping default/current/unrelated dirty workspaces unless explicitly requested.

Quick Start

Create a new workspace named <name> from the current checkout and report its path.

Frequently Asked Questions about workspace

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

FAQPage Schema
How do I manage jj workspaces under .workspaces without accidentally deleting the default one?

To manage jj workspaces safely, this skill automates creation, listing, and cleanup while enforcing safeguards that protect the default and active workspaces from accidental deletion.

What is the safest way to clean up finished jj workspaces after a merge?

The safest way to clean up finished jj workspaces is using the clean --all command, which removes only finished task workspaces and skips default, current, or dirty workspaces unless explicitly requested.

How do I create an isolated jj workspace for feature work from my current checkout?

You can create an isolated jj workspace by automating the creation of a named workspace under .workspaces from a specific revision or your current checkout, and the skill will report its path.

Can I list all jj workspaces and identify stale or finished entries without auto-deleting them?

Yes, you can list all named jj workspaces to highlight the current one and warn about finished or stale entries, ensuring the system does not auto-delete them during the review process.

Does jj workspace cleanup validate unlanded changes before removal?

Yes, jj workspace cleanup performs safe deletions with validation, requiring user confirmation before deleting any workspace that contains unlanded changes to prevent data loss.

When should I not use automated jj workspace deletion?

You should not use automated jj workspace deletion when targeting the default or active workspace, as the skill enforces repo-root detection and explicitly protects these environments from removal.