jj-vcs

Manage code changes with jj's mutable commit workflow.

9|1|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/tunnckoCore/zagora --skill jj-vcs-tunnckocore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jj-vcs
Source: https://github.com/tunnckoCore/zagora/tree/main/.opencode/skills/jj-vcs
Command: npx skills add https://github.com/tunnckoCore/zagora --skill jj-vcs-tunnckocore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jujutsu (jj) provides a Git-compatible VCS with mutable, rewritable commits, enabling you to craft clean, atomic changes without chaotic histories.

Core Features & Use Cases

  • Atomic commits and split/squash workflows to keep changes focused.
  • Described commits and change IDs for stable references even after rewrites.
  • Bookmark-based branching and seamless integration with existing Git workflows for library codebases.

Quick Start

Describe the change you intend to make, and follow the prompts to create an atomic, validated commit workflow with jj.

Frequently Asked Questions about jj-vcs

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

FAQPage Schema
How do I create atomic commits with mutable commit workflows?

Jujutsu's mutable commit workflow creates atomic commits by letting you describe intended changes first, then validating and generating focused commits with inline messages and stable change IDs.

What is the best way to rebase and split commits without losing history?

Rebasing and splitting commits without losing history is achieved through Jujutsu's mutable commits, which maintain stable change IDs even after rewrites, ensuring safe, non-throwing results during repository updates.

Can I use Jujutsu with existing Git workflows and library codebases?

Yes, Jujutsu integrates seamlessly with existing Git workflows through bookmark-based branching, making it suitable for managing library codebases that require a clean, atomic commit history.

How do I manage bookmarks and squash changes in a repository?

Bookmarks and squash changes are managed using deterministic command usage within repositories containing a .jj directory, allowing you to safely combine commits and maintain stable references throughout the workflow.

Does Jujutsu require a specific directory structure to function?

Jujutsu requires a repository containing a .jj directory to function, ensuring it can properly enforce deterministic command usage and validate workflows like absorb, split, and squash operations.