What problem does it solve?
Contributors working in Carbon repository checkouts that use Jujutsu (jj) instead of Git need clear guidance on which version control commands to run, and risk using the wrong tool or blocking commands that wait on terminal pagers.
Core Features & Use Cases
- Tool Detection: Detects whether Jujutsu is in use by checking for a
.jj directory, enforcing that jj and git are never mixed.
- Safe Command Invocation: Mandates the
--no-pager flag on every jj invocation to prevent commands from blocking on terminal paging.
- Common Workflows: Provides commands for syncing with remotes (
jj git fetch, jj new trunk), inspecting state (jj status, jj log, jj diff), and managing changes (jj commit, jj abandon, jj rebase -o trunk).
- Use Case: A contributor clones the Carbon repository, finds a
.jj directory, and uses this Skill to fetch from the remote, create a new change on top of trunk, and commit their work without ever touching git.
Quick Start
Check whether the repository root contains a .jj directory, and if so use the jj commands from this skill to fetch from the remote and create a new change on top of trunk.