Jujutsu Workflow

For agentic coding, prefer jj (Jujutsu) over raw git whenever a .jj/ repo is present — it is the superior local change layer. Git stays the canonical remote/PR/CI/audit interface: mutate with jj, verify with read-only Git.

1. Detect & gate first

Run ${CLAUDE_SKILL_DIR}/scripts/detect_jj_state.sh, or check manually:

• .jj/ present → jj repo: use jj, never mutating raw git.
• .jj/ and .git/ → colocated: mutate with jj, read with git, never touch the git index/staging.
• only .git/ → plain Git repo: do not introduce jj unless asked.

See references/git-interop.md.

2. Agent-safety rules (non-negotiable)

• Always --no-pager on output commands; set jj config set --user ui.paginate never.
• Always -m. Never run editor/TUI forms — bare jj describe|commit|squash, jj split (interactive), jj squash -i, jj resolve, jj diffedit — they hang agents.
• jj snapshots the working copy only when a jj command runs, not on every file write.