logoalt Hacker News

textlapse • today at 8:03 AM • 3 replies • view on HN

Does this work well with LLM workflows? Any advantages over git for say Claude or GPT or Gemini to stage changes in a better way?


Replies

nchmy • today at 10:56 AM

I think all the models do pretty well with jj now. I just added instructions and a skill to make sure they always use jj rather than git commands.

Only gap that I care about is jj workspaces<->git worktrees is not fully implemented. You can now auto create a worktree when you create a workspace, but not the reverse. There's prs for this though. I hope they get merged soon.

mhw • today at 9:57 AM

Codex seems to do pretty well with jj in my experience. I often use it to do things like resolving the conflicts in a rebased stack. The two main issues I found were having to remind it to use jj instead of git in a colocated repository, and it getting stuck when some commands open the interactive hunk selector or an editor.

I wrote a jj skill (https://github.com/mhw/jj-skill) that tries to address both of those issues, and explaining some higher-level workflows like the conflict resolution example I described above. It happily goes through the conflicts creating new commits off them, resolving the conflict, and then squashing the results.

VMG • today at 8:32 AM

The LLMs I use seem to handle it (I'm not sure about the token efficiency though). It could actually be more token efficient because I'm not rebasing as often.

Long-term I'm sure LLMs will have JJ in their training data.

➕ show 1 reply