Vi JJ Docs
Use local, authoritative sources (prefer jj help and upstream docs) to answer questions about jj without guessing command syntax.
Workflow (token-efficient, accuracy-first)
- •Confirm context: repo/workspace root (
jj root) and current state (jj status). - •For command syntax/flags: run
jj help <command>(orjj <command> -h) and quote only the relevant lines. - •For concepts: search docs in a
jjcheckout (typically./docs/) usingscripts/jj-doc-search.sh "<query>", then open only the needed section. - •Respond with the minimal command sequence and call out side effects (history rewriting, pushing bookmarks).
Quick start (common tasks)
- •Inspect:
jj status,jj log,jj diff - •Start/continue work:
jj new,jj edit <rev>,jj describe - •Rewrite history:
jj squash,jj split,jj rebase - •Undo:
jj undoorjj op log+jj op restore - •Bookmarks (branch-like names):
jj bookmark list|set|create|move|track|untrack - •Git remotes:
jj git fetch,jj git push(remember: pushes bookmarks, not revisions)
Examples: references/quickref.md. Revsets: references/revsets-quickref.md. Doc map: references/doc-index.md.
Accuracy rules
- •Do not invent flags, subcommands, or revset syntax; confirm via
jj helpor the matching doc page. - •Prefer stable revision selectors (
@,@-, bookmarks) over copying short IDs unless the user already has them. - •When recommending
jj git push, state exactly what will be pushed (e.g.,--bookmark X,--change Y, or--all).