commit-message-generator

Generate Conventional Commits messages from uncommitted Git changes.

4|10|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/NITRR-Official/CampusOS --skill commit-message-generator-nitrr-official
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message-generator
Source: https://github.com/NITRR-Official/CampusOS/tree/main/.agents/skills/commit-message-generator
Command: npx skills add https://github.com/NITRR-Official/CampusOS --skill commit-message-generator-nitrr-official

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The manual creation of commit messages can be time-consuming and prone to errors. This skill automates the process, ensuring consistent, well-structured commit messages.

Core Features & Use Cases

  • Commit Message Creation: Automatically generate commit messages based on uncommitted changes.
  • Change Categorization: Categorizes changes into Conventional Commit types like feat, fix, etc.
  • Scope Determination: Identifies the scope of changes within the codebase.
  • Multi-Commit Support: Suggests splitting multiple changes into separate commits if necessary.
  • User-Friendly Output: Provides clear, copy-paste-ready commit messages and staging commands.

Quick Start

Run the skill to generate a commit message for your current changes.

Frequently Asked Questions about commit-message-generator

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

FAQPage Schema
How do I automatically generate commit messages from uncommitted changes?

The skill analyzes uncommitted changes in Git to determine the scope and categorize them into Conventional Commit types like feat or fix, providing copy-paste-ready messages and staging commands.

How does this approach handle multiple logical changes in a single commit?

For multiple logical changes, the skill suggests splitting them into separate commits and generates distinct Conventional Commit messages with appropriate scopes for each change.

Do I need Git installed to categorize changes into Conventional Commits?

Yes, Git is required for the skill to analyze uncommitted changes and execute the generation of categorized Conventional Commit messages.

What is the best way to automate version control commit messages for code review?

To automate commit messages for code review, the skill reads uncommitted changes, categorizes them into Conventional Commit types, and outputs structured messages to streamline the review process.