commit-message

Generate conventional commit messages from staged Git changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mathfalcon/revendiste --skill commit-message-mathfalcon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/mathfalcon/revendiste/tree/main/.cursor/skills/commit-message
Command: npx skills add https://github.com/mathfalcon/revendiste --skill commit-message-mathfalcon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers automatically generate clear, conventional commit messages from their staged Git changes, reducing ambiguity and ensuring consistency across the project history.

Core Features & Use Cases

  • Conventional-commit-compliant messages: Subjects adhere to 50-72 character guidelines with an optional body that explains what changed and why.
  • Scope and clarity: Automatically indicate the affected components or modules when applicable.
  • Use Case: When preparing a release, run this Skill to produce a single, well-structured commit message summarizing all staged changes.

Quick Start

Run the skill against the current Git staging area to generate a conventional commit message, then copy and use it in your commit.

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 staged git changes?

To generate conventional commit messages from staged git changes, run the skill against your current Git staging area to produce a standardized subject and optional body summarizing the updates.

What is the best way to automate conventional commits for features and fixes?

The best way to automate conventional commits for features and fixes is to use a skill that analyzes your staged codebase changes and auto-generates compliant messages indicating affected components.

Does automated commit message generation work with large codebases?

Yes, automated commit message generation works with large codebases, handling features, fixes, refactors, docs, and chore updates by producing standardized subjects and detailed bodies when significant changes occur.

How do I ensure my git commit subjects adhere to the 50-72 character limit?

To ensure git commit subjects adhere to the 50-72 character limit, use an automation tool that enforces these length constraints while generating conventional commit messages from your staged changes.

Can I automatically note breaking changes in my conventional commit messages?

Yes, you can automatically note breaking changes in conventional commit messages by running an automation skill that detects significant staged updates and appends the necessary breaking change annotations.