Generating JJ Commit Messages

Conventional commit messages follow the `type(scope): description` format, where type is one of feat, fix, refactor, docs, test, chore, style, perf, ci, or build. The summary line must stay under 72 characters, optionally followed by a body with bullet points and a footer with attribution. This Skill generates these messages automatically based on your changes.

Conventional commits enforce a structured format that makes commit history readable and enables automated changelog generation and version bumping. Regular messages lack this consistency. Conventional commits improve project maintainability by standardizing how changes are documented.

Yes. JJ supports conventional commit messages just like Git. This Skill generates properly formatted conventional commits for JJ repositories, analyzing your changes to suggest the correct type and scope before you commit.

After modifying files, ask the Skill to generate a commit message and specify the context—such as whether it's a feature, bug fix, or refactor, and which module or component changed. The Skill outputs a formatted message ready for your `jj commit` command.

This Skill supports feat, fix, refactor, docs, test, chore, style, perf, ci, and build types. Each type categorizes the nature of the change, making commit history filterable and meaningful for tracking features, fixes, documentation updates, and infrastructure changes.