
Agentic Jujutsu
Run lock-free, agent-aware version control so several coding agents can commit on one repo without serial Git bottlenecks.
Overview
Agentic Jujutsu is an agent skill most often used in Build (also Ship, Operate) that provides self-learning, multi-agent version control with ReasoningBank trajectories and conflict-aware commits.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agentic-jujutsuWhat is this skill?
- JjWrapper API for status, commits, branches, and logs from agent scripts or skills
- ReasoningBank trajectories that record tasks, finalize with scores, and surface JSON suggestions with confidence
- Marketed as lock-free VC roughly 23x faster than Git for agent-heavy edit loops
- Automatic conflict resolution cited at 87% success for concurrent agent changes
- Quantum-resistant positioning for long-lived agent repository history
- Version 2.3.2 in skill metadata
- 23x faster than Git (README claim)
- 87% automatic conflict resolution success rate (README claim)
Adoption & trust: 654 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You run several coding agents on one repo and Git locking plus merge fights stall autonomous commits.
Who is it for?
Indie builders orchestrating parallel agent edits who want jj-style VC, trajectory logging, and suggestion-backed next steps in JavaScript.
Skip if: Solo humans using only standard Git with one sequential assistant and no need for agent-specific trajectories or a separate VC runtime.
When should I use this skill?
You need multiple AI agents modifying code simultaneously with lock-free version control, self-learning trajectories, or automatic conflict resolution.
What do I get? / Deliverables
Agents commit through JjWrapper with trajectories and suggestions so concurrent edits resolve faster and you keep an auditable agent-native history.
- Git-style commits and branches via JjWrapper
- ReasoningBank trajectories with finalize scores and JSON suggestions
- Concurrent multi-agent edit history without manual Git lock choreography
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Multi-agent commits and trajectories happen while you are actively building with agents, so the canonical shelf is Build. The skill is purpose-built for AI agent coordination and VC wrappers, which maps to agent-tooling rather than generic backend code.
Where it fits
Two agents implement auth and logout on separate branches while JjWrapper records trajectories and suggests the next commit message.
You wire JjWrapper into a custom agent harness so every tool call ends with status and a scored trajectory finalize.
Before tagging a release you pull agent commit logs and resolve remaining conflicts using the advertised automatic resolution path.
You keep a long-running agent sandbox repo on agentic-jujutsu to preserve quantum-resistant history and pattern suggestions across sprints.
How it compares
Agent-native version-control integration, not a drop-in replacement for GitHub PR review or a generic planning skill.
Common Questions / FAQ
Who is agentic-jujutsu for?
Solo and indie builders who run multiple AI coding agents on the same repository and need coordination beyond a single git user.
When should I use agentic-jujutsu?
During Build when agents branch and commit in parallel; during Ship when you reconcile agent history before release; and during Operate when you maintain long-lived agent-driven repos with learning-backed suggestions.
Is agentic-jujutsu safe to install?
It runs via npx and touches your filesystem and version history—review the Security Audits panel on this Prism page and pin versions before using on production repos.
SKILL.md
READMESKILL.md - Agentic Jujutsu
# Agentic Jujutsu - AI Agent Version Control > Quantum-ready, self-learning version control designed for multiple AI agents working simultaneously without conflicts. ## When to Use This Skill Use **agentic-jujutsu** when you need: - ✅ Multiple AI agents modifying code simultaneously - ✅ Lock-free version control (23x faster than Git) - ✅ Self-learning AI that improves from experience - ✅ Quantum-resistant security for future-proof protection - ✅ Automatic conflict resolution (87% success rate) - ✅ Pattern recognition and intelligent suggestions - ✅ Multi-agent coordination without blocking ## Quick Start ### Installation ```bash npx agentic-jujutsu ``` ### Basic Usage ```javascript const { JjWrapper } = require('agentic-jujutsu'); const jj = new JjWrapper(); // Basic operations await jj.status(); await jj.newCommit('Add feature'); await jj.log(10); // Self-learning trajectory const id = jj.startTrajectory('Implement authentication'); await jj.branchCreate('feature$auth'); await jj.newCommit('Add auth'); jj.addToTrajectory(); jj.finalizeTrajectory(0.9, 'Clean implementation'); // Get AI suggestions const suggestion = JSON.parse(jj.getSuggestion('Add logout feature')); console.log(`Confidence: ${suggestion.confidence}`); ``` ## Core Capabilities ### 1. Self-Learning with ReasoningBank Track operations, learn patterns, and get intelligent suggestions: ```javascript // Start learning trajectory const trajectoryId = jj.startTrajectory('Deploy to production'); // Perform operations (automatically tracked) await jj.execute(['git', 'push', 'origin', 'main']); await jj.branchCreate('release$v1.0'); await jj.newCommit('Release v1.0'); // Record operations to trajectory jj.addToTrajectory(); // Finalize with success score (0.0-1.0) and critique jj.finalizeTrajectory(0.95, 'Deployment successful, no issues'); // Later: Get AI-powered suggestions for similar tasks const suggestion = JSON.parse(jj.getSuggestion('Deploy to staging')); console.log('AI Recommendation:', suggestion.reasoning); console.log('Confidence:', (suggestion.confidence * 100).toFixed(1) + '%'); console.log('Expected Success:', (suggestion.expectedSuccessRate * 100).toFixed(1) + '%'); ``` **Validation (v2.3.1)**: - ✅ Tasks must be non-empty (max 10KB) - ✅ Success scores must be 0.0-1.0 - ✅ Must have operations before finalizing - ✅ Contexts cannot be empty ### 2. Pattern Discovery Automatically identify successful operation sequences: ```javascript // Get discovered patterns const patterns = JSON.parse(jj.getPatterns()); patterns.forEach(pattern => { console.log(`Pattern: ${pattern.name}`); console.log(` Success rate: ${(pattern.successRate * 100).toFixed(1)}%`); console.log(` Used ${pattern.observationCount} times`); console.log(` Operations: ${pattern.operationSequence.join(' → ')}`); console.log(` Confidence: ${(pattern.confidence * 100).toFixed(1)}%`); }); ``` ### 3. Learning Statistics Track improvement over time: ```javascript const stats = JSON.parse(jj.getLearningStats()); console.log('Learning Progress:'); console.log(` Total trajectories: ${stats.totalTrajectories}`); console.log(` Patterns discovered: ${stats.totalPatterns}`); console.log(` Average success: ${(stats.avgSuccessRate * 100).toFixed(1)}%`); console.log(` Improvement rate: ${(stats.improvementRate * 100).toFixed(1)}%`); console.log(` Prediction accuracy: ${(stats.predictionAccuracy * 100).toFixed(1)}%`); ``` ### 4. Multi-Agent Coordination Multiple agents work concurrently without conflicts: ```javascript // Agent 1: Developer const dev = new JjWrapper(); dev.startTrajectory('Implement feature'); await dev.newCommit('Add feature X'); dev.addToTrajectory(); dev.finalizeTrajectory(0.85); // Agent 2: Reviewer (learns from Agent 1) const reviewer = new JjWrapper(