jujutsu-workflow

Enforce Change ID-based commits and bookmark usage in Jujutsu workflows.

1|Updated Sep 16, 2025

Search Tags:#workflow #jujutsu #jj #bookmark #change-id

Ready to run

npx skills add https://github.com/sk8metalme/ai-agent-setup --skill jujutsu-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jujutsu-workflow
Source: https://github.com/sk8metalme/ai-agent-setup/tree/main/plugins/jujutsu-workflow/skills/jujutsu
Command: npx skills add https://github.com/sk8metalme/ai-agent-setup --skill jujutsu-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jujutsu (jj) バージョン管理システムのワークフロー支援。Change IDベース管理を中心に、ブックマークの活用を最小限に抑えつつ、ドキュメント作成とPR作成を効率化します。

Core Features & Use Cases

Change IDベースのコミット管理
ブックマークは必要な時だけ活用
ドキュメント作成とPRフローの統合支援

Quick Start

Quick Start: JJで新機能ブックマークを作成し、最初のChange-IDコミットを開始します。

Frequently Asked Questions about jujutsu-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage commits using Change IDs in Jujutsu instead of traditional Git workflows?▼

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.

What's the difference between using bookmarks and Change IDs in a jj workflow?▼

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.

Can I create pull requests directly from Jujutsu Change IDs without switching to Git?▼

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.

How do I set up Change ID-based commits and bookmarks for AI agent development workflows?▼

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.

What are the limitations of relying solely on Change IDs without Git commands?▼

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.