jj:describe

Generate and apply one-line commit descriptions for jj via jj describe.

1|Updated Feb 4, 2023

Search Tags:#automation #commit #description #jj #version-control #one-line #prefix-detection

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consistent, concise commit descriptions for jj-based workflows to improve traceability and readability of change histories.

Core Features & Use Cases

Automatically generate a one-line description from a set of changes using jj show and jj diff.
Enforce a single-line commit message and a consistent prefix derived from the file paths.
Apply the description with jj describe <rev> -m "<description>" to update the commit message in the repository.

Quick Start

Describe a commit by providing a concise summary of the changes and let the tool apply it with jj describe <rev> -m "<description>".

Frequently Asked Questions about jj:describe

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

FAQPage Schema

How do I generate concise jj commit messages automatically?▼

To generate concise jj commit messages, the Skill analyzes changes using jj show and jj diff, derives a project prefix from file paths, and applies a validated one-line description with jj describe.

Can I enforce a single-line commit description format for jj version control?▼

Yes, you can enforce a single-line commit description for jj version control by validating the generated message format before applying it to ensure it remains strictly on one line.

How does prefix detection work for jj commit descriptions?▼

Prefix detection for jj commit descriptions works by analyzing the file paths in the diff to automatically derive a consistent project prefix for the commit message.

Does this jj commit description tool work for large diffs with complex file paths?▼

Yes, the jj commit description tool works for large diffs with complex file paths by summarizing changes across the entire revision to generate an applicable one-line description.

What is the best way to apply a generated description to a jj revision?▼

The best way to apply a generated description to a jj revision is to run jj describe <rev> -m "<description>", finalizing the commit message directly in the repository.