commit-helper

Generate structured commit messages from Git and JJ repository changes.

1|Updated Nov 1, 2025

Search Tags:#git #workflow #commit #jj #version-control #message

Ready to run

npx skills add https://github.com/rselbach/dotfiles --skill commit-helper-rselbach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-helper
Source: https://github.com/rselbach/dotfiles/tree/main/claude/skills/commit-helper
Command: npx skills add https://github.com/rselbach/dotfiles --skill commit-helper-rselbach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you generate clear, structured commit messages from repository changes, improving traceability across Git and JJ workflows.

Core Features & Use Cases

Consistent Message Format: Produce a concise summary (present tense, under 50 chars), a detailed rationale, and an optional list of affected files.
VCS-Agnostic Workflow: Works with both JJ and Git repos, adapting to staged and unstaged changes and diffs.
Guided Compliance: Enforces style guidelines to improve readability and consistency across commits.

Quick Start

Describe the current changes to create a clear commit message for the upcoming commit.

Frequently Asked Questions about commit-helper

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

FAQPage Schema

How do I generate a commit message from staged and unstaged changes?▼

To generate a commit message from staged and unstaged changes, describe the current repository diffs. The tool produces a concise present-tense summary under 50 characters, a detailed rationale, and an optional list of affected files.

What makes a good git commit message format for traceability?▼

A good git commit message format for traceability includes a concise present-tense summary under 50 characters, a detailed rationale explaining the changes, and an optional list of affected files. This structure improves readability and consistency across commits.

Does this commit message generator work with both Git and JJ version control workflows?▼

Yes, this commit message generator works with both Git and JJ version control workflows. It adapts to staged and unstaged changes and diffs in either repository type, functioning as a VCS-agnostic tool to enforce consistent message guidelines.

How do I enforce a consistent commit message style across my repository?▼

To enforce a consistent commit message style across your repository, apply guided compliance rules during message generation. This ensures every commit features a concise summary, a detailed rationale, and affected files, improving overall readability and traceability.

What is the best way to write a concise present-tense commit summary?▼

The best way to write a concise present-tense commit summary is to keep it under 50 characters while capturing the core change. The generated message then adds a detailed rationale and optional affected files to complete the structured format.