generating-jj-commit-messages

Generate commit messages from jj diffs with summaries and affected components.

Updated Aug 30, 2024

Search Tags:#automation #git #diff #code-review #jj #commit-message

Ready to run

npx skills add https://github.com/alistairstead/dotfiles2 --skill generating-jj-commit-messages-alistairstead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generating-jj-commit-messages
Source: https://github.com/alistairstead/dotfiles2/tree/main/claude/.claude/skills/generate-jj-commit-message
Command: npx skills add https://github.com/alistairstead/dotfiles2 --skill generating-jj-commit-messages-alistairstead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps transform your JJ diffs into clear, concise commit messages, saving time when writing commits or reviewing staged changes.

Core Features & Use Cases

Auto-generated Summary: Produce a short, present-tense summary limited to 50 characters.
Detailed Description: Include a concise rationale and what changed.
Affected components: Identify files or modules touched.

Quick Start

Run jj diff --git to view changes Then prompt to generate a commit message for the diff I will return a commit message with a short summary, a detailed description, and a list of affected components.

Frequently Asked Questions about generating-jj-commit-messages

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

FAQPage Schema

How do I generate commit messages from jj diffs?▼

Generate commit messages from jj diffs by running `jj diff --git` to view your changes, then prompt this Skill to produce a structured commit message. It returns a short summary under 50 characters, a detailed description explaining what changed and why, and a list of affected components.

Can I automate commit message creation during code review?▼

Yes. This Skill automates commit message creation during code review by analyzing jj diffs and generating clear, structured messages. It produces a concise summary, detailed rationale, and component list, eliminating manual writing and ensuring consistency across reviews.

What should a good commit message include?▼

A good commit message includes a short summary under 50 characters in present tense, a detailed description prioritizing what changed and why over grammar, and an affected components list. This Skill generates all three elements automatically from your jj diff.

Does this work with jj version control?▼

Yes. This Skill is designed specifically for jj version control. It parses jj diffs using `jj diff --git` output and generates commit messages tailored to jj workflows, supporting both staged changes and code review preparation.

How do I identify which files changed in my commit?▼

This Skill automatically identifies affected files and modules by analyzing your jj diff and including them in the generated commit message. The affected components list appears alongside the summary and detailed description.

What's the best way to write commit messages for code review?▼

Use this Skill to generate structured commit messages during code review. It produces clear summaries, explains the rationale behind changes, and lists affected components—reducing review friction and ensuring messages document intent and scope accurately.