git-commit-message

Generates commit messages based on detected patterns and repository conventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JuanGarciaFuture/mobile-practice --skill git-commit-message-juangarciafuture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-message
Source: https://github.com/JuanGarciaFuture/mobile-practice/tree/main/.cursor/skills/git-commit-message
Command: npx skills add https://github.com/JuanGarciaFuture/mobile-practice --skill git-commit-message-juangarciafuture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate commit messages that align with a repository's established conventions, reducing manual effort and improving history readability.

Core Features & Use Cases

  • Analyze the last 40 commits to detect pattern, style, and tense.
  • Generate a compliant subject line for staged changes based on the identified pattern.
  • Support common styles (conventional commits, simple descriptions, ticket prefixes, and emoji prefixes) to fit diverse projects.

Quick Start

Generate a commit message for the currently staged changes that follows the repository's commit conventions.

Frequently Asked Questions about git-commit-message

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

FAQPage Schema
How do I automatically generate a git commit message that matches my repository's conventions?

Generating conventional commits is achieved by analyzing the repository's recent commit history to detect patterns and styles. The Skill then creates a matching subject line and an optional body emphasizing the why, outputting a ready-to-use git commit command for your staged changes.

What commit message patterns and styles are supported by this automation workflow?

Supported commit message patterns include conventional commits, simple descriptions, ticket prefixes, and emoji prefixes. The automation adapts to your repository's specific tone by analyzing recent history to ensure the generated subject line aligns with the detected style.

How do I create a commit message for staged changes that includes the reasoning behind the code modification?

To create a commit message for staged changes that includes reasoning, the Skill generates a compliant subject line and an optional body. This body describes the change and emphasizes the why, providing a complete ready-to-use git commit command.

Can I use this automation to generate commit messages for a project using ticket prefixes?

Yes, you can use this automation for projects using ticket prefixes. The workflow identifies ticket prefixes and other common styles by analyzing the last 40 commits, ensuring the generated commit message matches your project's specific conventions.

What is the best way to maintain code quality and consistent git history across diverse projects?

The best way to maintain code quality and consistent git history is to generate commit messages that align with established repository conventions. This automation analyzes recent commits to detect tense and style, reducing manual effort and improving history readability across diverse projects.