How does GCM analyze my code changes?

The skill runs 'git diff --cached' to see exactly what has been staged, allowing it to provide an accurate summary of the modifications.

Will it match the existing style of my project?

Yes, the workflow includes checking the last five commits in your log to understand the project's specific tone and naming conventions.

Does it handle the 50/72 character rule for git commits?

Absolutely. It prioritizes keeping subject lines under 50 characters for readability while moving detailed explanations into the body.

Does this skill follow the Conventional Commits standard?

Yes, it uses standard types such as feat, fix, refactor, chore, and docs to ensure your commit history is structured and machine-readable.

Git Commit Message Generator

Name: Git Commit Message Generator
Author: takuan-osho

bytakuan-osho

0•

Developer Tools

Generates professional, standardized Git commit messages by analyzing staged code changes and following Conventional Commits patterns.

The GCM skill automates the process of writing high-quality Git commit messages by meticulously analyzing your staged changes and project history. It ensures every commit follows the Conventional Commits specification, providing a clear structure with a concise subject line under 50 characters and a detailed body explaining the reasoning and impact of the changes. This skill is essential for teams looking to maintain a clean, searchable, and professional repository history that is optimized for automated changelog generation and peer review.

Key Features

01Style matching by reviewing recent repository commit history.

02Detailed body generation focusing on the 'why' and technical impact.

03Strict enforcement of the Conventional Commits specification (feat, fix, refactor, etc.).

04Automatic subject line length constraint management.

050 GitHub stars

06Automated analysis of staged git changes using git diff.

Use Cases

01Quickly documenting complex refactors or bug fixes with technical accuracy.

02Standardizing commit message formats across collaborative development teams.

03Preparing repositories for automated release notes and semantic versioning.

Key Features

01Style matching by reviewing recent repository commit history.

02Detailed body generation focusing on the 'why' and technical impact.

03Strict enforcement of the Conventional Commits specification (feat, fix, refactor, etc.).

04Automatic subject line length constraint management.

050 GitHub stars

06Automated analysis of staged git changes using git diff.

Use Cases

01Quickly documenting complex refactors or bug fixes with technical accuracy.

02Standardizing commit message formats across collaborative development teams.

03Preparing repositories for automated release notes and semantic versioning.