onevcat-jj

What problem does it solve?

Many repositories are managed locally with jj instead of git, and using git commands in those contexts causes confusion, lost time, and incorrect workflows. This Skill clarifies when to prefer jj, how jj's change-centric model differs from git, and how to perform common version-control tasks safely in jj-managed projects.

Core Features & Use Cases

• Change-first workflow: Explains jj's model where the working copy is a change, there is no staging area, and every file edit belongs to the current change.
• Common operations: Covers inspecting state, describing and switching changes, splitting and rebasing changes, creating bookmarks for remote pushes, and recovery via undo and operation restore.
• Agent patterns: Provides agent-friendly patterns such as starting the next task with jj new, interrupting and resuming work with jj edit/jj new, and skeleton planning with sequential changes.
• Real-world example: Use jj in a colocated repository to implement a multi-step refactor by creating skeleton changes, editing each change in order, and publishing only the necessary bookmarks to remote.

Quick Start

Start a fresh task by running jj new and then set the change description with jj describe -m "feat: short summary" before implementing your changes.