jj-resolve-conflicts
Resolve conflicts in the current `jj` commit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Resolve conflicts in the current `jj` commit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Make a set of things (code, prose, config, docs) consistent along a dimension the user names, by picking a canonical form and conforming every member to it.
Remove illegal states from data structures by redesigning their types so the illegal states cannot be represented at all.
Remove unnecessary comments from code: tombstones, redundant restatements, and comments a well-named variable or function would replace.
Perform a task with a worker agent, critique it with an adversary agent, and apply the accepted critiques with a reconciler agent.
Replace jargon and imported metaphors in code and prose with concrete, domain-fitting terms a reader understands without translation.
Create a new Claude Code skill following the conventions of existing skills.
| name | jj-resolve-conflicts |
| description | Resolve conflicts in the current `jj` commit. |
| argument-hint | [extra guidance on resolving] |
| allowed-tools | ["Bash(jj resolve *)","Bash(jj op log *)","Bash(jj undo *)"] |
Resolve conflicts in the current jj commit.
jj st
$ARGUMENTS
jj resolve --listjj log -r '::@ & conflicts()' shows the
conflicted ancestry. Read the descriptions of the commits whose changes
collided to understand each side's intentjj resolve --tool :ours <file>
(side #1) or jj resolve --tool :theirs <file> (side #2)jj file show -r <revision> <file>jj resolve --list should report none and
jj st should show no conflicted pathspackage.json,
Makefile, CI config) and run them. If no signals are found, ask the user@ automatically. Run
jj log -r 'conflicts()'; any conflicts that remain are distinct and need
their own resolutionjj materializes conflicts as a diff to apply, not two alternatives:
<<<<<<< Conflict 1 of 1
%%%%%%% Changes from base to side #1
-old line
+side #1's replacement
+++++++ Contents of side #2
side #2's version of the region
>>>>>>> Conflict 1 of 1 ends
%%%%%%% section is a diff: lines starting with - are the base, lines
starting with + are side #1's edit, and unprefixed lines are context+++++++ section is side #2's full content for the regionThe next jj command snapshots a wrong resolution. To get the conflict back, find
the resolution's operation with jj op log and revert it with
jj undo <operation>. With no argument, jj undo reverts the most recent
operation.