Contact
Development

Jujutsu Workflow

Stop coding agents losing work and corrupting branch state in git: use Jujutsu (jj) as the local change layer — reversible op-log undo, conflicts-as-data, non-interactive history surgery — while Git stays the canonical remote/PR/CI interface. Proven with evals to beat pure git for agents.

Latest release v1.1.0

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace 
    /plugin install jujutsu-workflow@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection 
    npx skills add https://github.com/netresearch/jujutsu-workflow-skill

    Requires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Uses the skills CLI from skills.sh Installs skill instructions. Extra plugin hooks, commands and external runtime tools are not installed by this route.

  3. composer require PHP project, as a package 
    composer require netresearch/jujutsu-workflow-skill

    Allow the Composer skill installer to activate and approve skill registration when prompted. Requires netresearch/composer-agent-skill-plugin Discovers trusted skill packages and registers their instructions in AGENTS.md. Runtime tools may need separate setup.

  4. composer skills:add PHP project, direct source 
    composer skills:add netresearch/jujutsu-workflow-skill

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Provided by netresearch/composer-agent-skill-plugin Pins source repositories without a Packagist package and records them in composer.skills.lock. Runtime dependencies remain separate.

What you can do with it

  • A coding agent works in a repository where jj is installed or allowed.
  • You use jj / Jujutsu, patch stacks, or speculative iterative edits.
  • You need to recover agent edits with jj op log / jj undo / jj op restore.
  • You split agent-generated changes, hand off a PR from jj, or update a PR after review comments.
  • You want to replace fragile git reset / checkout / stash / rebase recovery with reversible jj operations.

What you get back

  • A local change described or committed with jj, with unrelated edits split.
  • A Git-visible branch/bookmark pushed for PR creation, never targeting a protected branch.
  • A final verification block reporting both jj and Git state plus any tests or lints that were run.

What it expects in your project

  • A Git-backed repository (colocated jj/Git preferred), with jj installed locally.
  • Project governance is respected: branch protection, CODEOWNERS, commit conventions, signed commits, CI gates.
  • External access: none beyond the Git remote (GitHub/GitLab) the project already uses.

Tags

  • development
  • devops