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.

1.27x

Quality

74%

Does it follow best practices?

Impact

88%

1.27x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./jujutsu/SKILL.md

Evaluation results

85%

28%

Bug Fix in a Jujutsu Repository

Starting work workflow

Criteria

Without context

With context

Validate blank revision

100%

Create new commit if needed

37%

Describe before coding

100%

Inline message flag on desc

100%

Inline message flag on squash

100%

No jj commit

100%

Imperative verb phrase

100%

Sentence case no period

100%

Verify after mutations

Use diff --git

100%

90%

29%

Untangling Mixed Changes in a Jujutsu Repository

Splitting commits without interactive tools

Criteria

Without context

With context

No jj split

100%

No jj squash -i

100%

Uses jj restore

100%

Diff uses --git flag

100%

Verify after each mutation

Inline -m on all desc/squash

50%

100%

Atomic commit per change

100%

Imperative verb messages

100%

No full stop in messages

100%

Correct separate commits

100%

90%

Publishing a Feature Branch After Team Updates

Remote sync and bookmark management

Criteria

Without context

With context

Fetch before rebase

100%

Rebase after fetch

100%

Explicit bookmark move

100%

Push uses -b flag

100%

No raw git push

100%

Change IDs in references

100%

No git commands in non-colocated context

100%

Inline -m flags

100%

Verify with jj st

Correct push sequence

100%

Repository: danverbraganza/jujutsu-skill
Commit: 72207e4

Evaluated: 15 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Bug Fix in a Jujutsu Repository Untangling Mixed Changes in a Jujutsu Repository Publishing a Feature Branch After Team Updates

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.