Curating Jujutsu Commits

Detect mixed concerns in Jujutsu commits and propose split or squash actions.

78|6|Updated May 19, 2017

Search Tags:#developer tools #code review #version control #refactoring #git history #jujutsu #commit curation

Ready to run

npx skills add https://github.com/edmundmiller/dotfiles --skill curating-jujutsu-commits

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Curating Jujutsu Commits
Source: https://github.com/edmundmiller/dotfiles/tree/main/config/claude/plugins/jj-workflow-plugin/skills/commit-curation
Command: npx skills add https://github.com/edmundmiller/dotfiles --skill curating-jujutsu-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of organizing and refining your commit history, making code reviews easier and ensuring a clean, logical progression of changes without manual tedium.

Core Features & Use Cases

Intelligent Commit Splitting: Automatically identifies and suggests splitting commits that mix unrelated concerns (e.g., tests and code), promoting atomic changes.
Automated Commit Squashing: Detects and helps combine "WIP" or "fixup" commits into logical, coherent units, cleaning up your history.
Use Case: Before submitting a pull request, use this Skill to automatically identify and suggest how to split a large commit that contains both feature work and documentation updates, ensuring each part can be reviewed independently and efficiently.

Quick Start

Help me curate my current Jujutsu commits. I have some WIP commits and mixed changes.

Frequently Asked Questions about Curating Jujutsu Commits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I split commits that mix unrelated changes in jujutsu?▼

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.

What's the best way to clean up WIP and fixup commits before a pull request?▼

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.

When should I curate my commit history in jujutsu?▼

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.

Can jujutsu automatically organize disorganized commits?▼

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.

What indicators does jujutsu recognize in commit messages for cleanup?▼

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.

How do I organize feature work and documentation into separate commits?▼

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.