use-jujutsu

Translate Git workflows into JJ equivalents for version control tasks.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/lhohan/agentfiles --skill use-jujutsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-jujutsu
Source: https://github.com/lhohan/agentfiles/tree/main/agents/dotagents/.agents/skills/use-jujutsu
Command: npx skills add https://github.com/lhohan/agentfiles --skill use-jujutsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jujutsu (jj) provides a Git-like workflow with its own commands; this guide offers clear, JJ-centric instructions to perform common VCS tasks without leaving JJ.

Core Features & Use Cases

  • Maps common Git tasks to jj equivalents (commit, push, history, revsets)
  • Enforces safe, non-destructive workflows and basic guardrails
  • Use Case: transitioning a team from Git to jj while preserving history and collaboration models

Quick Start

Ask me to perform a jj status to see the current workspace state.

Frequently Asked Questions about use-jujutsu

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

FAQPage Schema
How do I translate Git commit and history commands to Jujutsu equivalents?

To translate Git workflows to Jujutsu, map standard Git commit and history tasks to jj equivalents. This guide provides clear, JJ-centric instructions for performing common version control tasks without leaving the jj environment.

What is the best way to search commit history using jj revsets?

Searching commit history with jj revsets involves using JJ-specific query syntax to find specific revisions. This guide covers history searches and revsets to help you locate and interact with past commits safely.

Can I use Jujutsu for safe version control without losing data during branching?

Yes, you can use Jujutsu for safe version control because it enforces non-destructive workflows and basic guardrails. It guides safe commands for branching and commits to prevent accidental history loss.

How do I transition a team from Git to jj while preserving collaboration models?

Transitioning a team from Git to jj requires mapping common VCS tasks to jj equivalents while preserving history and collaboration models. This guide supports this exact use case by enforcing core JJ usage rules.

What are the limitations or guardrails when using jj for version control?

When using jj for version control, limitations are managed through documented error handling and basic guardrails. The guide enforces safe, non-destructive workflows and core JJ usage rules to prevent unsafe commands.