Curating Jujutsu Commits

Splitting mixed commits in jujutsu isolates concerns like tests, docs, and code into separate, atomic changes. Use jj diff to identify mixed content, then propose splits by concern type, ensuring each commit addresses a single logical unit for cleaner review and history.

Detect WIP, fixup, and temp indicators in commit messages, then squash or combine them into coherent logical units. This consolidates exploratory work into polished changes, making your PR history clear and reducing reviewer friction.

Curate commits when your history mixes unrelated concerns, contains WIP or fixup changes, or before submitting PRs or sharing code. Organizing commits before these milestones prevents reviewers from navigating tangled history and ensures logical progression.

Jujutsu commit curation guides splitting and squashing by detecting mixed concerns and WIP patterns, then proposes actions. While not fully automatic, it intelligently identifies reorganization opportunities and integrates with jj log and jj diff for guided refinement.

Jujutsu detects WIP, fixup, and temp markers in commit descriptions as signals for consolidation. Recognizing these patterns helps the Skill propose which commits to squash together into coherent units before finalizing your history.

Use jj diff to inspect large commits containing both code and docs, then propose splits by concern. Separating feature work from documentation into independent commits allows each part to be reviewed, tested, and versioned independently.