git-commit

Analyze git diffs to generate Conventional Commits messages.

Updated Jan 30, 2026

Search Tags:#automation #git #commit #version-control #conventional-commits #diff-analysis #interactive-commit

Ready to run

npx skills add https://github.com/juanjaragavi/social-media-genius --skill git-commit-juanjaragavi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/juanjaragavi/social-media-genius/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/juanjaragavi/social-media-genius --skill git-commit-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized, semantic git commits using the Conventional Commits specification. Analyze diffs to determine type, scope, and message.

Core Features & Use Cases

Auto-detects type and scope from changes to generate conventional commit messages.
Generates messages from diffs with an imperative, present-tense style.
Interactive commit mode allows optional type/scope/description overrides and staged changes grouping.

Quick Start

Analyze the current diffs and generate a conventional commit message for the staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate conventional commits automatically from git diffs?▼

Conventional commits standardize semantic versioning by enforcing a structured format. They clarify the type, scope, and description of changes, which helps automate release notes and maintain a clean project history.

Can I override the auto-generated commit type and scope interactively?▼

Yes, interactive commit mode allows you to override the auto-generated type, scope, and description. This enables manual adjustments while still grouping staged changes within a standardized messaging workflow.

How do I ensure my commit messages use imperative present tense?▼

The commit generation process analyzes your staged changes and outputs messages in imperative, present-tense style. This ensures your conventional commit messages follow standard git formatting guidelines directly from the analyzed diff.

Do I need any external dependencies to create conventional commit messages from diffs?▼

No external dependencies are required to create conventional commit messages. The skill operates independently to analyze your git diffs and output structured messages directly within your version control workflow.

What is the best way to standardize semantic git commits across a development team?▼

The best way to standardize semantic git commits is to enforce the Conventional Commits specification. Automating message generation from diffs ensures consistent type, scope, and description formatting across all team contributions.