commit-message

Generate conventional commit messages from Git diffs and staged changes.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/LittleBreak/pet-soul --skill commit-message-littlebreak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/LittleBreak/pet-soul/tree/main/.claude/skills/commit-message
Command: npx skills add https://github.com/LittleBreak/pet-soul --skill commit-message-littlebreak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers generate clear, conventional commit messages by analyzing git diffs and staged changes.

Core Features & Use Cases

  • Automated commit messages: Create consistent subjects and bodies from diffs
  • Scope inference: Detect affected files or components to suggest a scope
  • Guidance & compliance: Enforces conventional commits and provides Co-Authored-By metadata

Quick Start

Review the current staged changes and request a conventional commit message.

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 git diffs automatically?

To generate conventional commit messages from git diffs, stage your changes and request automated analysis. The tool parses diffs to infer affected scopes and formats structured subjects, bodies, and co-authored-by metadata for consistency.

What is a conventional commit message and when do I need to use it for my code changes?

A conventional commit message standardizes subjects and bodies by change type, such as feature development or bug fixes. You need it for refactors and other code changes to enforce consistency across software projects.

Can I automatically detect the scope for my commit messages from staged changes?

Yes, you can detect the scope for commit messages from staged changes by analyzing affected files and components. The tool automatically infers the correct scope from your git diff to suggest appropriate metadata.

Does this automated commit message generator work with different types of code changes?

Yes, the automated commit message generator works with feature development, bug fixes, refactors, and other code changes. It analyzes git diffs and applies conventional commit formatting regardless of the specific modification type.

What is the best way to enforce conventional commits and include co-authored-by metadata?

The best way to enforce conventional commits and include co-authored-by metadata is to automate generation from git diffs. This ensures consistent subject and body formatting while appending required co-authored-by metadata automatically.