commit

Generate Conventional Commits compliant git commit messages from code changes.

3|Updated Mar 7, 2026

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

Ready to run

npx skills add https://github.com/gokulkrishh/skills --skill commit-gokulkrishh

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

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

Core Features & Use Cases

Conventional Commits: Generates commits adhering to the Conventional Commits specification.
Automated Analysis: Analyzes code changes (staged or unstaged) to determine commit type, scope, and breaking changes.
Use Case: After making several bug fixes, use this Skill to generate a fix commit with an appropriate scope and a descriptive body explaining the resolution.

Quick Start

Use the commit skill to generate a conventional commit for my staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate a conventional commit message automatically from staged changes?▼

To generate a conventional commit message, this Skill analyzes your staged or unstaged git diffs to automatically determine the commit type, scope, and breaking changes for clear version control history.

What is the conventional commits specification for formatting git commit messages?▼

The conventional commits specification structures git commit messages by enforcing a specific format for the title, body, and footer, ensuring consistent version control and clear project history documentation.

Do I need the git CLI installed to analyze diffs and create conventional commits?▼

Yes, you need the git CLI installed, as the Skill requires it to analyze staged or unstaged code changes and generate compliant conventional commit messages based on those diffs.

How does automated commit analysis determine breaking changes in my code?▼

Automated commit analysis determines breaking changes by evaluating your code diffs against the conventional commits specification, then flags these changes in the generated commit message footer.

Can I use this for both staged and unstaged code changes in version control?▼

Yes, you can use this Skill for both staged and unstaged code changes, as it analyzes the git diff to determine the appropriate commit type and scope for your version control history.

What's the best way to format a fix commit with a scope and descriptive body?▼

The best way to format a fix commit is to let the Skill analyze your bug fix diffs, automatically generating a conventional commit with an appropriate scope and a descriptive body explaining the resolution.