Can I use jj with existing Git repositories?

Yes, you can initialize a colocated repository using 'jj git init --colocate' within an existing Git project to start using Jujutsu immediately without losing Git history.

Why is my Vite project slow when using jj?

Vite's file watcher often monitors the .jj metadata directory; excluding '**/.jj/**' in your vite.config.js server.watch.ignored settings usually resolves these performance issues.

How do I hide jj files from VS Code?

Add the .jj directory to the 'files.watcherExclude' and 'search.exclude' sections in your .vscode/settings.json to improve IDE performance and clean up search results.

Should I use the jj CLI or library for scripting?

Use the CLI for language-agnostic scripts and rapid prototyping, or the Rust library for high-performance, type-safe integrations if you are willing to manage breaking API changes.

What is Jujutsu (jj) colocation?

Colocation allows you to use both Jujutsu and Git in the same working directory, enabling access to Git-based tools and CI/CD pipelines while benefiting from jj's advanced features.

Jujutsu Repository Manager

Name: Jujutsu Repository Manager
Author: edmundmiller

byedmundmiller

•

Deployment & DevOps

Configures and optimizes Jujutsu (jj) version control repositories with seamless tool integration and colocation strategies.

About

This skill streamlines the setup and maintenance of Jujutsu (jj) repositories, guiding users through critical decisions like Git colocation and automated tool integration. It provides expert advice on resolving common conflicts with file watchers in Vite and Vitest, configures IDE settings for VS Code and IntelliJ, and offers architectural guidance for building programmatic integrations using either the jj library or CLI. Whether you are migrating from Git or starting a new project, this skill ensures your version control environment is performant, stable, and correctly configured for modern development stacks.

Key Features

Optimized configurations for Vite and Vitest to prevent file watcher conflicts
40 GitHub stars
Pre-configured IDE exclude patterns for VS Code and IntelliJ
Automated Jujutsu repository initialization and Git colocation setup
Best practices for repository structure and performance tuning
Architectural guidance for building programmatic integrations via CLI or Rust library

Use Cases

Setting up a new colocated Jujutsu and Git project for team migration
Developing custom scripts or tools that interact with Jujutsu repositories
Resolving performance lag or hanging in Vite/Vitest projects caused by jj metadata

About

Key Features

Optimized configurations for Vite and Vitest to prevent file watcher conflicts
40 GitHub stars
Pre-configured IDE exclude patterns for VS Code and IntelliJ
Automated Jujutsu repository initialization and Git colocation setup
Best practices for repository structure and performance tuning
Architectural guidance for building programmatic integrations via CLI or Rust library

Use Cases

Setting up a new colocated Jujutsu and Git project for team migration
Developing custom scripts or tools that interact with Jujutsu repositories
Resolving performance lag or hanging in Vite/Vitest projects caused by jj metadata