jj

Standardize jj commit messages and manage change workflows.

1|Updated Feb 4, 2023

Search Tags:#workflow #cli #learning #diff #jj #version-control #commit-message

Ready to run

npx skills add https://github.com/jbott/nix-config --skill jj-jbott

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jj
Source: https://github.com/jbott/nix-config/tree/main/home-manager/programs/claude-code/skills/jj
Command: npx skills add https://github.com/jbott/nix-config --skill jj-jbott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a concise, standardized reference for using the jj version-control CLI, ensuring consistent commit messages, workflows, and collaboration patterns.

Core Features & Use Cases

Standardizes commit descriptions with a project-prefix convention to improve traceability.
Offers commands and patterns for diff, show, and diff-stat workflows to analyze changes efficiently.
Includes guidance on splitting commits, squashing changes, and managing bookmarks to organize work.
Supports best practices for reviewing history and coordinating across team members.

Quick Start

Create a new commit with a descriptive project-prefix message following the guidelines above.

Frequently Asked Questions about jj

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

FAQPage Schema

How do I enforce consistent commit messages in jj?▼

You can split and squash commits in jj using specific CLI commands to organize changes before finalizing history. This workflow allows you to refine commits by combining related modifications or separating distinct changes for cleaner project tracking.

How do I analyze code changes with jj diff and show workflows?▼

You analyze code changes with jj by utilizing diff, show, and diff-stat command patterns. These workflows allow you to efficiently review modifications, inspect specific file differences, and understand the scope of changes before finalizing your version history.

What is the recommended way to manage bookmarks in jj?▼

The recommended way to manage bookmarks in jj involves applying included guidance to organize and coordinate work across team members. Bookmarks help track distinct lines of development and streamline the history review process within collaborative projects.

Can I use jj for collaborative version control without complex dependencies?▼

Yes, you can use jj for collaborative version control without complex dependencies, as it requires no external components to standardize workflows. It operates independently to track changes, enforce commit formats, and coordinate team history reviews.

When should I squash changes instead of splitting commits in jj?▼

You should squash changes in jj to combine related modifications into a single cohesive commit, whereas splitting commits separates distinct logical changes. Following the provided workflow guidance ensures your history remains organized and reviewable.