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.
99
100%
Does it follow best practices?
Impact
100%
1.28xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Agent-safe jj history curation script
-m on jj new
0%
100%
-m on jj squash
100%
100%
-m on jj describe
100%
100%
No interactive commands
100%
100%
jj st after mutations
100%
100%
Uses absorb
100%
100%
Quoted revsets
100%
100%
Change IDs preferred
100%
100%
Non-interactive identity config
100%
100%
ui.paginate never
50%
100%
workflow_output.txt produced
100%
100%
Bookmark and PR push workflow
Explicit bookmark set
100%
100%
jj git push not git push
100%
100%
No jj git pull
100%
100%
jj git fetch used
100%
100%
Rebase after fetch
100%
100%
@- after jj commit
80%
100%
Independent branch from trunk
100%
100%
Bookmarks don't auto-advance
100%
100%
No jj pull mentioned
100%
100%
-m flags present
40%
100%
Agent config and workspace setup
ui.editor set
100%
100%
ui.diff-formatter = ":git"
0%
100%
ui.paginate = "never"
0%
100%
JJ_CONFIG launch pattern
100%
100%
Sibling directory rule
100%
100%
jj edit before work
0%
100%
Absolute paths for agents
0%
100%
Stale workspace fix
100%
100%
Cleanup: forget + rm
100%
100%
User identity in config
100%
100%
Three ui settings explained
37%
100%
40067f1
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.