theo-jujutsu

Automate jj version control workflows in colocated or Git-backed repositories.

Updated Jan 29, 2026

Search Tags:#version control #bookmarks #jj #history editing #git interop #colocated workflow

Ready to run

npx skills add https://github.com/get-theo-ai/agent-skills --skill theo-jujutsu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: theo-jujutsu
Source: https://github.com/get-theo-ai/agent-skills/tree/main/skills/theoai-jujutsu
Command: npx skills add https://github.com/get-theo-ai/agent-skills --skill theo-jujutsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JJ-based version control can be confusing when teams mix with Git or when you want to avoid a staging area. This skill clarifies and streamlines jj workflows, enabling predictable commits and history editing.

Core Features & Use Cases

Git-compatible workflow with jj: manage commits, diffs, and logs without a staging area.
Bookmark-centric history: create, navigate, and rewrite commits using jj bookmarks.
Colocated Git interop: work with a Git repo on colocated mode and push/pull across remotes.
Use Case: When collaborating on a repository that uses jj, you can perform edits, rebase, squash, and manage history with a consistent jj workflow.

Quick Start

Install or ensure jj is available on your system and run a basic workflow:

Initialize or open a jj repository
Make a file change
Use jj new or jj describe to commit
Use jj log or jj st to review history

Frequently Asked Questions about theo-jujutsu

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

FAQPage Schema

How do I use jj for version control in a colocated Git repository?▼

Jj version control in a colocated Git repository operates natively on your existing Git history, allowing you to manage commits and diffs without a staging area while maintaining full interop with Git remotes.

What is the best way to manage bookmarks and rewrite history with jj?▼

Managing bookmarks and rewriting history with jj involves using bookmark-centric commands to navigate, create, and rebase commits predictably, streamlining collaborative workflows without manual staging.

Can I push and pull changes to Git remotes using jj workflows?▼

Git remote interop is fully supported in colocated jj workflows, enabling standard push and pull operations across remotes while using jj to handle local history editing and bookmark management.

Do I need a staging area to create commits with jj?▼

Creating commits with jj does not require a staging area; you can make file changes and directly use jj new or jj describe to commit, bypassing Git's index entirely for a faster workflow.

What prerequisites are needed to automate jj version control workflows?▼

Automating jj version control workflows requires a local jj installation and standard shell tooling to execute commands, operating without network exfiltration or destructive actions.

How does jj interop handle history editing when mixed with Git teams?▼

Jj interop handles mixed Git team workflows by applying predictable history edits, squashes, and rebases locally via jj, then synchronizing the results seamlessly to the underlying Git repository.