skills.rest
anahelenasilva
anahelenasilvaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

generate-commit-message

Generate Conventional Commits messages from git diff analysis.

Updated Nov 23, 2025
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/anahelenasilva/meridiano-nestjs --skill generate-commit-message
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: generate-commit-message
Source: https://github.com/anahelenasilva/meridiano-nestjs/tree/main/.cursor/skills/generate-commit-message
Command: npx skills add https://github.com/anahelenasilva/meridiano-nestjs --skill generate-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commit messages, ensuring they adhere to the Conventional Commits specification and accurately reflect code changes.

Core Features & Use Cases

  • Conventional Commits: Generates messages following the <type>[scope]: <description> format.
  • Change Analysis: Analyzes git diff to determine the commit type, scope, and description.
  • Use Case: After making several code changes, you can ask this Skill to generate a commit message that summarizes your work, like feat(auth): implement user registration endpoint.

Quick Start

Use the generate-commit-message skill to create a commit message for your staged changes.

Frequently Asked Questions about generate-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 diff?▼

Generating conventional commit messages from git diff involves analyzing staged or unstaged code changes to identify the commit type, scope, and imperative description. This process formats outputs like feat or fix to accurately reflect code modifications.

What are conventional commits and when do I need them for version control?▼

Conventional commits are a specification for structuring commit messages using types like feat, fix, or docs, along with optional scopes and descriptions. You need them for version control to standardize commit histories and automate release notes.

How do I write a git commit message for breaking changes?▼

To write a git commit message for breaking changes, you generate a conventional commit with a specific type and scope, optionally including a body and footer. The footer explicitly documents the breaking change to ensure clear code review tracking.

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

You can automatically determine the commit type and scope from staged changes by analyzing the code differences. The generated message identifies appropriate types like feat or fix and applies an optional scope based on the modified files.

Does this commit message generator work with unstaged code differences?▼

This commit message generator works with unstaged code differences by analyzing them to produce conventional commit messages. It evaluates the modifications to determine the correct type, scope, and description without requiring a staged environment.

Related Skills

Explore More Software Engineering Skills→
HirogaKatageriHirogaKatageri
5

Conventional Commit Generator

Convert git diffs into Conventional Commits messages with optional bodies and footers.

Community
Advanced
dascarddascard
2

chinese-commit-conventions

Standardize Git commit messages with Conventional Commits for Chinese teams.

Community
Intermediate
co-labs-coco-labs-co
1

conventional-commits-release

Validate commit messages and PR titles with commitlint for automated semantic-release versioning.

Official
Intermediate
k97k97
4

git-commit

Analyzes git diffs to generate standardized conventional commit messages.

Community
Intermediate