jujutsu-workflow

Change ID-driven workflow in Jujutsu organizes commits around immutable Change IDs rather than branch names. Each commit receives a unique Change ID, enabling you to track and reorganize work without Git rebasing, simplifying collaborative development and PR creation while maintaining commit identity across revisions.

Bookmarks in Jujutsu are lightweight pointers used selectively for named references, while Change IDs are the primary organizational unit for commits. This workflow minimizes bookmark usage, relying instead on Change ID governance to reduce complexity and enforce consistent commit management during agent development.

Yes. This workflow integrates PR creation into the jj workflow by leveraging Change IDs as the source of truth, eliminating the need to switch to Git commands. You organize and track changes through jj, then create PRs directly from Change ID-based commits, streamlining the handoff to collaborative review.

Initialize a jj repository, create a bookmark for your feature branch, make your first commit tagged with a Change ID, then follow the prescribed directory checks and command-asking patterns for agent orchestration. The workflow enforces Change ID governance throughout development to maintain consistency in agent-driven collaboration.

This workflow requires full commitment to jj as the primary tool and avoids Git entirely, which may limit interoperability with Git-based CI/CD pipelines or teams unfamiliar with Jujutsu. Success depends on your team's ability to adopt jj conventions and operate within Change ID-centric organization.