jj
$ brew install jjVersion control, stacked changes, and git-compatible history from the terminal.
- jj fits git & github well, especially for version control, stacked changes, and git-compatible history from the terminal.
- 4,783 homebrew installs (30d).
- Easy to automate.
- Good fit for coding-agent workflows and repeatable scripts.
- Output is mostly text-first, so verify results before scripting around it.
Jj guide
Version control, stacked changes, and git-compatible history from the terminal. Built by Jujutsu.
Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.
When to apply
- version control, stacked changes, and git-compatible history from the terminal.
- You need git workflows in both local dev and CI.
- You need version control.
- You need stacked changes.
- You need git-compatible history.
Quick reference
brew install jjjj --versionjj git init --colocateOpen CLI × skills.sh
Open CLI integrates jj with the right skills.sh companions so you get the tool and the workflow together.
Git Workflow
Recommended pairingOpen CLI recommends this skills.sh skill because it fits git workflows. Use cleaner branches, reviews, and merge flows around Git-based CLIs.
$ npx skills add https://github.com/supercent-io/skills-template --skill git-workflowUse jj together with the Git Workflow skills.sh skill. Start with safe inspection commands, summarize what you find, and ask before any step with side effects.
Why this tool
- jj fits git & github well, especially for version control, stacked changes, and git-compatible history from the terminal.
- 4,783 homebrew installs (30d).
- Easy to automate.
Watch-outs
- Output is mostly plain text.
- Start with read-only or dry-run commands.
Example workflow
1. jj git init --colocateSafe start
Install jj.
Run `jj --version` first.
Start with `jj git init --colocate`.
Install the CLI and make sure it is on your PATH.