commit-message

Generate conventional commit messages from staged, unstaged, and untracked git changes.

70|13|Updated Jan 26, 2026

Search Tags:#git #developer tools #code review #version control #conventional commits #commit message

Ready to run

npx skills add https://github.com/oprogramadorreal/optimus-claude --skill commit-message-oprogramadorreal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/oprogramadorreal/optimus-claude/tree/main/skills/commit-message
Command: npx skills add https://github.com/oprogramadorreal/optimus-claude --skill commit-message-oprogramadorreal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of well-formatted commit messages, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

Conventional Commits: Generates messages adhering to the Conventional Commits specification.
Change Analysis: Analyzes staged, unstaged, and untracked git changes to infer commit intent.
Multi-repo Support: Handles commit message generation for projects with multiple git repositories.
Use Case: After making several changes to your codebase, run this skill to get a perfectly formatted commit message like feat(auth): add email validation without manually crafting it.

Quick Start

Use the commit-message skill to get a suggested conventional commit message for your current git 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 from git changes?▼

Conventional commit messages are generated by analyzing staged, unstaged, and untracked git changes. The tool inspects your codebase diffs and infers the commit intent to suggest a formatted message like feat(auth): add email validation.

What is the conventional commits specification and why use it for version control?▼

The conventional commits specification standardizes commit messages to improve repository navigability and enable programmatic parsing. Using this format ensures consistency and clarity across your project's version control history.

Can I generate commit messages for multiple git repositories in a workspace?▼

Yes, you can generate commit messages for multiple git repositories. The tool explicitly supports multi-repo workspaces, allowing you to analyze changes and suggest conventional commits across different repositories within your project environment.

Does generating commit messages require running git commands for diff analysis?▼

Yes, generating commit messages requires git commands for diff and status analysis. The tool executes these commands to inspect your current changes, analyze the modifications, and infer the appropriate conventional commit type and scope.

What is the best way to automate conventional commit formatting for code review?▼

Automating conventional commit formatting is best achieved by analyzing git changes before committing. This tool evaluates your diffs and status to automatically output correctly formatted conventional commits, streamlining the code review process.