commit-msg

Generate Git commit messages from staged changes with ticket IDs.

3|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/nmoinvaz/speedy-gonzales --skill commit-msg-nmoinvaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-msg
Source: https://github.com/nmoinvaz/speedy-gonzales/tree/main/skills/commit-msg
Command: npx skills add https://github.com/nmoinvaz/speedy-gonzales --skill commit-msg-nmoinvaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Automated Message Generation: Creates multiple commit message options based on staged changes.
  • Convention Adherence: Follows best practices for title and body formatting, including imperative mood and line wrapping.
  • Ticket ID Integration: Automatically includes relevant ticket IDs (e.g., PROJ-123) in the commit message.
  • Use Case: After making several code changes, use this Skill to get suggestions for a commit message that clearly explains the changes and adheres to your team's standards.

Quick Start

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

Frequently Asked Questions about commit-msg

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

FAQPage Schema
How do I generate a Git commit message from staged changes?

To generate a Git commit message from staged changes, this Skill analyzes your diffs and provides multiple message options. It ensures consistency by adhering to formatting guidelines for the title and body, including line wrapping.

Can I automatically include ticket IDs in my Git commit messages?

Yes, you can automatically include ticket IDs in your Git commit messages. This Skill analyzes your staged diffs to identify ticket IDs, such as PROJ-123, and integrates them directly into the suggested commit message options.

What is the best way to format Git commit messages for project history?

The best way to format Git commit messages is using the imperative mood and concise explanations. This Skill automates this by generating well-formatted titles and bodies from your diffs, ensuring clarity and consistency in your project history.

How does automated commit message generation work with code diffs?

Automated commit message generation works by analyzing your staged code diffs to identify key changes and ticket IDs. It then creates multiple message options that follow best practices for title and body formatting.

Does this commit message generator work without external dependencies?

Yes, this commit message generator works without external dependencies. It operates independently to analyze your staged changes and produce multiple message options adhering to specified formatting guidelines.

Why should I use an automated tool for Git commit message generation?

You should use an automated tool for Git commit message generation to ensure consistency and clarity in your project history. It eliminates manual effort by analyzing diffs and providing convention-adherent message options.