Kenjutu: per-commit code review with hunk-level tracking that survives rebases

[Yuki-bun]

I've been building a local code review tool called kenjutu designed around jj's workflow.
The core idea: mark individual hunks as reviewed, and have that progress survive amends, rebases, and squashes — because review state is tied to change IDs, not commit hashes.

The problem it solves: When you're working on or reviewing a stack of commits there's no good way to track what you've actually verified. You can read through a diff, but if you amend the commit later, you lose track of what you already checked.
Kenjutu gives every commit a "remaining diff" that shrinks as you review.

You can also leave inline comments on changes locally before pushing. (Inspired by difit) There's a CLI tool (kjc) that outputs these comments as structured JSON — so coding agents can consume your review feedback directly.

Available as a desktop app (Tauri) and a Neovim plugin, both backed by the same Rust engine.

2026-03-15.1.00.08.mov

559009542-237a3d93-0f1e-4d28-9c98-b2067e73cd26.1.mov

Repo: https://github.com/Yuki-bun/kenjutu

Please give me feedback!

[joyously]

Having just looked at a PR where I felt that a change was missing, how would this tool handle that case?

[Yuki-bun]

Kenjutu doesn't have a specific feature for that case — it tracks what's in the diff, not what's
missing from it. One thing you can do is leave a comment around where the change should be added,
but the review tracking itself won't help surface missing code. That's a hard problem — let me know
if you've seen tools that handle it well!

[joyously]

In the case I was referring to, it was missing changes in the docs file to describe the code changes, so there wouldn't be a place to say that....