jujutsu
**REQUIRED** - Always activate FIRST on any git/VCS operations (commit, status, branch, push, etc.), especially when HEAD is detached. If `.jj/` exists -> this is a Jujutsu (jj) repo - raw git commands can corrupt data. Essential git safety instructions inside. DO NOT IGNORE.
87
83%
Does it follow best practices?
Impact
93%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
36%Scripting a Jujutsu Repository Workflow
Non-interactive jj workflow scripting
No-pager on log
0%
100%
No-pager on show/diff
0%
100%
Inline -m flag for commits
100%
100%
Git diff format
0%
100%
Two separate commits
100%
100%
Commit message: sentence case
100%
100%
Commit message: no full stop
100%
100%
Commit message: imperative verb
100%
100%
Status check present
100%
100%
Output captured
100%
100%
88%
10%Publishing a Feature Branch with Jujutsu
Bookmark management and push workflow
Bookmark move before push
90%
50%
Correct push command
100%
100%
No raw git push
100%
100%
Status verification after commits
0%
100%
No-pager on log
0%
100%
Inline -m commit messages
100%
100%
Two atomic commits
100%
100%
Commit message format
100%
80%
Output captured
100%
100%
92%
Reorganizing Scattered Changes Across Commits
Describe-first workflow and absorb
Describe before changes
100%
77%
jj absorb present
100%
100%
No-pager on log
100%
100%
No-pager on diff/show
100%
100%
Git diff format
0%
100%
Inline -m flags
100%
100%
Change ID preference
100%
50%
Status verification
100%
100%
Separate commits
100%
100%
Commit message format
100%
100%
- Repository
- danverbraganza/jujutsu-skill
- Commit
b066831
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
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.