jj-history-cleanup

To clean up Git commit history, you can reorganize commits to ensure each is atomic, logically ordered, and clearly described. This skill facilitates immediate, non-interactive history rewriting to consolidate intermediate commits into review-ready narratives.

Squashing WIP commits in Git is achieved by rewriting history to combine related changes into single, well-defined commits. This skill supports immediate squashing operations to consolidate rapid development commits without complex interactive sessions.

Yes, you can reorder and reword Git commits without interactive rebasing by using immediate, non-interactive operations. This approach facilitates history rewriting and logical ordering while providing robust error handling via an operation log.

Jujutsu supports dropping and splitting commits to refine Git history. It facilitates atomic commit creation and efficient history rewriting through immediate operations, allowing you to drop unnecessary changes or split large commits into logical units.

An operation log provides robust error handling during Git history rewriting by tracking immediate, non-interactive operations. If an error occurs during commit reordering, squashing, or splitting, the log ensures operations can be safely managed and recovered.

You need to refactor Git commit history after a period of rapid development with many small, intermediate commits. Refactoring ensures your project history forms a clear narrative with atomic, logically ordered, and well-described commits before submission.