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.
Installation
Nimm den Weg, der zu deinem Projekt passt — alle führen zum selben Skill.
-
Claude Code über diesen Marketplace /plugin install jujutsu-workflow@netresearch-claude-code-marketplace -
npx beliebige Agent-Skills-CLI npx skills add https://github.com/netresearch/jujutsu-workflow-skill --skill jujutsu-workflowUniverselle Agent-Skills-CLI von
skills.sh— funktioniert in Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI und 30+ weiteren Agents. -
composer require PHP-Projekt, als Paket composer require netresearch/jujutsu-workflow-skillSetzt
netresearch/composer-agent-skill-pluginvoraus — bindet Agent Skills als Composer-Dependencies in PHP-Projekte ein, erkennt Skills automatisch, generiert AGENTS.md. -
composer skills:add PHP-Projekt, direkte Quelle composer skills:add github:netresearch/jujutsu-workflow-skillKommt aus
netresearch/composer-agent-skill-plugin— pinnt Skill-Repos direkt ohne Packagist-Veröffentlichung, persistiert incomposer.skills.lock.
Wofür du den Skill einsetzt
- 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
Was du zurückbekommst
- 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.
Was der Skill im Projekt erwartet
- 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.