Jujutsu (jj) — the Git-compatible version control system. Activate ONLY when a .jj/ directory is present in the project or when jj/jujutsu is explicitly mentioned. Do NOT activate for plain git repos without .jj/. Use for any VCS operations in jj-managed projects: commit, push, pull, branch, bookmark, rebase, squash, merge, diff, log, status, working copy, change ID, revset, fileset, template, configuration, workspaces.
100
100%
Does it follow best practices?
Impact
100%
1.23xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Agent CI configuration and workflow script
Pagination disabled
100%
100%
Editor sentinel set
100%
100%
Git diff format
100%
100%
User identity present
100%
100%
JJ_CONFIG env var used
100%
100%
-m flag on all commit commands
100%
100%
Status check after mutation
100%
100%
Revset expression quoted
100%
100%
No interactive split/squash
100%
100%
No deprecated -d flag
100%
100%
Non-linear work and branching off trunk
--no-edit for independent branch
0%
100%
Branch off trunk
100%
100%
Change IDs used for references
100%
100%
Single-quoted revsets
0%
100%
jj st after mutations
100%
100%
-m flag always present
100%
100%
Bookmark set before push
100%
100%
-r not --revision
100%
100%
No deprecated -d flag
100%
100%
No interactive commands
100%
100%
Parallel agents workspace setup
Workspaces as siblings
0%
100%
--no-edit for task commits
25%
100%
Absolute paths in agent instructions
100%
100%
Agent workspace cd instruction
100%
100%
Merge commit with multiple parents
100%
100%
Status check after merge
100%
100%
workspace forget used
100%
100%
rm -rf for workspace directories
100%
100%
-m on all commit commands
100%
100%
Stale workspace guidance
0%
100%
d20109a
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.