commit-message

Analyze git changes and generate conventional commit messages.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/NihaalManaf/LDR-Island --skill commit-message-nihaalmanaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/NihaalManaf/LDR-Island/tree/main/.cursor/skills/commit-message
Command: npx skills add https://github.com/NihaalManaf/LDR-Island --skill commit-message-nihaalmanaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzing code changes and producing consistent, ready-to-use commit messages saves time and reduces manual error in version history.

Core Features & Use Cases

  • Generate conventional commit messages from a set of changed files to standardize project history.
  • Batch and group unrelated changes into logical commits for cleaner reviews and releases.
  • Use case: before committing, run the tool to automatically suggest messages for all modified files and review or adjust as needed.

Quick Start

Run the tool to analyze your current changes and receive a ready-to-use 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 automatically generate conventional commit messages from git changes?

You can generate conventional commit messages by running a command-line workflow that analyzes your git changes, groups files by context, and suggests messages based on configured patterns and file-type hints.

What is the best way to batch unrelated code changes into logical git commits?

Batching unrelated changes involves analyzing modified files across your project, grouping them by context, and suggesting separate conventional commit messages for each logical group to ensure cleaner reviews.

Can I analyze staged git changes before finalizing my commit history?

Yes, you can analyze staged git changes before committing. The tool reviews the staged files and suggests ready-to-use conventional commit messages that you can adjust as needed.

Does this commit message generator work without external dependencies?

Yes, the commit message generator works without external dependencies, using internal scripts to analyze changes and apply conventional commit patterns based on file-type hints.

Why should I use conventional commits instead of writing manual git commit messages?

Using conventional commits standardizes your project version history, saves time analyzing code changes, and reduces manual error by automatically grouping files and suggesting precise messages.