commit-message-writer

Generates formatted commit messages from staged changes.

1|Updated Mar 24, 2026

Search Tags:#automation #git #commit #cli #diff #conventional-commits

Ready to run

npx skills add https://github.com/jeremylongshore/j-rig-skill-binary-eval --skill commit-message-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message-writer
Source: https://github.com/jeremylongshore/j-rig-skill-binary-eval/tree/main/packages/core/fixtures/valid
Command: npx skills add https://github.com/jeremylongshore/j-rig-skill-binary-eval --skill commit-message-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit history requires consistent formatting, but deriving messages from diffs is error-prone and manual work. The Commit Message Writer automates generating conventional commit messages directly from the currently staged changes.

Core Features & Use Cases

Reads the staged diff (git diff --staged) to analyze changes.
Infers the commit type (feat, fix, docs, refactor, etc.), scope, and a concise subject following the conventional commits format.
Validates the subject length and formatting, producing a ready-to-commit message suitable for inclusion in a push.

Quick Start

Provide the staged changes (git diff --staged) and I will output a conventional commit message.

Frequently Asked Questions about commit-message-writer

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

FAQPage Schema

How do I generate conventional commit messages from staged git diffs?▼

To generate conventional commit messages from staged git diffs, provide the output of git diff --staged to the Skill. It analyzes the changes and infers the type, scope, and subject to output a properly formatted message.

Can I automatically infer the commit type and scope from git staged changes?▼

Yes, you can automatically infer the commit type and scope from git staged changes. The Skill reads the staged diff and determines the appropriate type, such as feat or fix, along with the scope and a concise subject.

What is the best way to format conventional commits for a consistent git history?▼

The best way to format conventional commits for a consistent git history is to automate message derivation from staged changes. This ensures the subject length and formatting are validated and follow the type(scope): subject structure.

Does the commit message writer validate subject length and formatting?▼

Yes, the commit message writer validates subject length and formatting. It processes the staged diffs and applies validation rules to produce a ready-to-commit message suitable for inclusion in a push.

When do I need to use conventional commits for my git workflow?▼

You need to use conventional commits for your git workflow when you require a consistent commit history. Deriving messages from diffs manually is error-prone, so automating the process ensures proper formatting across all staged changes.