Name: Describe
Author: joncol

Generate a concise commit message for a jj commit and apply it with jj describe.

Arguments

Optionally accepts a single jj revision (revset) as an argument (e.g. @, @-, a change ID, or any valid revset resolving to one commit). If no argument is given, defaults to @ (the current working copy).

Steps

Let REV be the argument if provided, otherwise @.
Run jj diff -r "$REV" to see the changes in that commit.
If there are no changes, inform the user and stop.
Analyze the diff and write a commit message following these rules:
- First line: short summary (under 70 characters), imperative mood (e.g. "Add", "Fix", "Update", not "Added", "Fixed", "Updated")
- If the change is scoped to a specific module/component, prefix with it (e.g. "kakoune: Add Python LSP support")
- No period at the end of the first line
- Only add a body (separated by blank line) if the why isn't obvious from the summary

Generate a concise commit message for a jj commit and apply it with jj describe.

Arguments

Steps

Let REV be the argument if provided, otherwise @.
Run jj diff -r "$REV" to see the changes in that commit.
If there are no changes, inform the user and stop.
Analyze the diff and write a commit message following these rules:
- First line: short summary (under 70 characters), imperative mood (e.g. "Add", "Fix", "Update", not "Added", "Fixed", "Updated")
- If the change is scoped to a specific module/component, prefix with it (e.g. "kakoune: Add Python LSP support")
- No period at the end of the first line
- Only add a body (separated by blank line) if the why isn't obvious from the summary

Describe

Arguments

Steps

Describe

Arguments

Steps

Coding Agent (bash-first)

Fix

Commit

Init

Github Copilot Upgrader

Rebuilding Flutter Tool