Netresearch Skills Marketplace
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 v0.1.0

Install

Pick whichever fits your project — they all reach the same skill.

  1. Claude Code via this marketplace 
    /plugin install jujutsu-workflow@netresearch-claude-code-marketplace
  2. npx any Agent Skills CLI 
    npx skills add https://github.com/netresearch/jujutsu-workflow-skill --skill jujutsu-workflow

    Universal Agent Skills CLI from skills.sh — works across Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI and 30+ more agents.

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

    Requires netresearch/composer-agent-skill-plugin — resolves Agent Skills as Composer dependencies in PHP projects, auto-discovers skills, generates AGENTS.md.

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

    Provided by netresearch/composer-agent-skill-plugin — pins skill repos directly without going through Packagist, locks them in composer.skills.lock.

What you can do with it

  • 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

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