commit-message

Generate conventional commit messages from staged diff analysis.

Updated Jul 3, 2026

Search Tags:#git #version control #commit #developer workflow #conventional commits #code changes

Ready to run

npx skills add https://github.com/Reidond/Banshee --skill commit-message-reidond

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/Reidond/Banshee/tree/main/.claude/skills/commit-message
Command: npx skills add https://github.com/Reidond/Banshee --skill commit-message-reidond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from writing commit messages by analyzing code changes and producing concise, consistent commit descriptions that explain intent.

Core Features & Use Cases

Change Analysis: Reviews staged or unstaged diffs to identify the change type, affected scope, and purpose.
Conventional Formatting: Creates commit subjects and optional bodies that follow established commit conventions and project style.
Use Case: When finishing a software task, use this Skill to turn a complex set of changes into a clear commit message ready for version control.

Quick Start

Ask the commit-message skill to generate a commit message for my current changes.

Frequently Asked Questions about commit-message

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

FAQPage Schema

How do I generate conventional commit messages from code changes automatically?▼

Conventional commits follow a structured format that prefixes commit messages with types like feat, fix, or chore to communicate intent. You need this format to standardize version control history, automate changelog generation, and clarify the purpose of code changes across a project.

Can I create a commit message from staged and unstaged diffs in my developer workflow?▼

To write a git commit message for a complex set of changes, first review the staged diff and detect the project's commit style. Then, summarize the code modifications into a concise, conventional commit subject and optional body that explains the change intent.

What is the best way to write clear git commit messages for version control?▼

The best way to write clear git commit messages for version control is to analyze the code changes and project history directly. Applying conventional formatting to the detected change type and scope produces consistent, intent-focused descriptions that remove guesswork.

Do I need to manually specify the commit type when generating a conventional commit message?▼

You do not need to manually specify the commit type when generating a conventional commit message. The process analyzes your staged diff and project history to automatically detect the change type and style, producing a correctly formatted commit subject.