Jj split

🤖 My Claude Code config!

Install

npx -y skills add TomerAberbach/claude-config --skill jj-split

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

3.1 KB, as published. Nobody here has run it

Split the current jj commit into multiple focused, self-contained, easy to review commits.

jj show --git

$ARGUMENTS

One concern per commit: e.g. bug fix, feature, refactor, or config change
Each commit passes all checks: format, lint, typecheck, build, test
Tests travel with the code they test
Refactors are never mixed with behavioral changes
Prefer thin vertical slices, one complete feature end-to-end, over horizontal layers
No orphaned code: every added API, abstraction, or stub must be used within the same commit. Don't split so small that dead code is introduced

Read the diff above. If the commit is already small and self-contained, tell the user and stop
Identify logical groupings and order them from most foundational to most dependent. When a boundary is ambiguous, keep changes together
Infer verification commands from project signals (e.g. package.json, Makefile, CI config). If no signals are found, ask the user
Present the plan as a numbered list:
- Commit N: <imperative-mood description>: <file or hunk list>
- One sentence justifying each split boundary
- The verification commands you will run after each split
- Ask for confirmation before proceeding
Split each commit except the last. After each split, edit the newly created parent commit (jj edit @-) and run the verification commands
Ensure every resulting commit has a description using jj describe
After all splits, run jj log -r 'ancestors(@, <commit count>)' and show the resulting stack

Use jj split with file patterns to put specific files in the first commit:

jj split -m "<first commit description>" -- <files for first commit>

The remaining files stay in the second commit.

When a single file contains changes that belong in different commits, use file manipulation:

Edit the file to contain only the changes for the first commit (remove hunks that belong later)
Run jj new to start the next commit
Re-edit the file to restore the hunks removed in step 1
Verify with jj log -r '@-::@' and jj diff -r @-

For when verification fails because some changes are in the wrong commit.

# Move from child to parent
jj squash --from @+ --into @ -- <files>

# Move from parent to child
jj squash --from @ --into @+ -- <files>

When the boundary falls inside a file, edit the file directly: