jj-hunk

Splitting mixed changes into clean commits using jj requires non-interactive hunk selection. You automate this by listing hunks and building a per-file action spec to guide logical commit separation without interactive UI prompts.

Non-interactive hunk selection for jj is a programmatic method to create focused commits. It satisfies deterministic command interfaces and structured spec-based execution for predictable version-control operations across split, commit, or squash workflows.

To selectively squash changes across multiple files in a worktree, you craft a spec detailing per-file actions and apply it with the squash operation. This automates selective squashing based on the generated spec.

Performing a partial commit in jj for specific hunks is possible by generating a per-file action spec. You execute the commit operation based on this spec to selectively include desired hunks deterministically.

Yes, jj-hunk works for separating a mixed refactor and feature into distinct commits. You run the list command to view hunks, craft a spec, and apply it with the split operation to create clean, logically separated commits.

The limitation of automating partial commits with a spec-based approach is that it requires deterministic command interfaces and structured spec execution. You must manually define per-file actions, which removes the flexibility of interactive UI selection.