commit-message

Generates conventional commit messages from staged git changes.

4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/platxa/platxa-skill-generator --skill commit-message-platxa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/platxa/platxa-skill-generator/tree/main/catalog/commit-message
Command: npx skills add https://github.com/platxa/platxa-skill-generator --skill commit-message-platxa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of well-formatted commit messages, ensuring consistency and adherence to the Conventional Commits specification, saving developers time and improving project history clarity.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes staged git changes to suggest commit type, scope, and description.
  • Conventional Commits Compliance: Formats messages according to the widely adopted standard.
  • Use Case: After making several code changes, you can run this skill to get a perfectly formatted commit message like feat(api): add user authentication endpoint without manually thinking about the type, scope, or imperative mood.

Quick Start

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

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

To generate conventional commit messages, this Skill analyzes your staged git changes to detect the change type, suggests a scope based on file paths, and formats the message according to the Conventional Commits specification.

What is the conventional commits format and how does an automated generator determine the scope?

The conventional commits format standardizes commit messages with a type, scope, and description. This generator determines the scope by analyzing your staged file paths and identifies the type based on the nature of the code changes.

Does this commit message generator work with my existing git workflow?

Yes, this commit message generator integrates with your existing git workflow by analyzing staged changes and supporting automated commit message creation directly within your development process.

What is the best way to automate git commit message creation for multiple file changes?

The best way to automate git commit message creation is to stage your code changes and run this Skill to produce a formatted message like `feat(api): add user authentication endpoint` without manually determining the type or scope.

Can I use this tool to format commit types like feat and fix without manual input?

Yes, you can format commit types without manual input because the Skill detects whether your staged changes represent a feature, fix, or other type, and formats the output accordingly based on the Conventional Commits specification.