Generate and apply one-line commit descriptions for jj via jj describe.
npx skills add https://github.com/jbott/nix-config --skill jj-describe
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
Generating consistent, concise commit descriptions for jj-based workflows to improve traceability and readability of change histories.
Describe a commit by providing a concise summary of the changes and let the tool apply it with jj describe <rev> -m "<description>".
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
jbottDisplays jj working copy status, trunk commits, and file diffs summaries.
karithamAutomate version control workflows using JJ commands for history, diffs, and commits.
cryfsManage version control workflows with JJ, a Git-compatible system.
missdeerCreate local git commits with conventional commit message formatting.
