commit

Generate Conventional Commit messages from staged changes and git history.

11|Updated Apr 16, 2026

Search Tags:#automation #git #workflow #coding-standards #version-control #commit-message #conventional-commits

Ready to run

npx skills add https://github.com/berkcangumusisik/claude-code-practices --skill commit-berkcangumusisik

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Staged değişiklikleri inceleyip Conventional Commits formatında net ve standart bir commit mesajı oluşturur, sürüm geçmişinin okunabilirliğini artırır.

Core Features & Use Cases

Staged değişikliklerden otomatik olarak commit mesajı üretir ve mesajı belirlenen tip, kapsam ve istersen gövde/footers ile şekillendirir.
Sürüm kontrol standartlarına uyum sağlar; feat, fix, refactor, docs gibi tip seçeneklerini kullanır ve gereken sınırlamaları uygular.
Geniş kullanım senaryolarında faydalıdır: yeni özellik geliştirme, hata düzeltme, bakım çalışması, dokümantasyon güncellemeleri gibi durumlarda bütünleşik mesaj üretimi sunar.

Quick Start

Staged değişiklikleri kullanın ve Conventional Commit mesajını otomatik olarak üretmesini sağlayın.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages from staged git changes?▼

To generate conventional commit messages from staged changes, the Skill analyzes your git diff, status, and log to automatically format the type, scope, and body. It outputs a properly formatted commit message.

What is the conventional commits format for version control workflows?▼

The conventional commits format structures version control messages using specific types like feat, fix, refactor, or docs, along with an optional scope and body to improve commit history readability.

How do I automate commit message formatting for features and fixes?▼

Automate commit message formatting by analyzing staged changes to determine the correct type, such as feat or fix, and applying scope and body constraints to enforce coding standards.

Does this conventional commit generator work with existing git history?▼

Yes, the conventional commit generator works with existing git history by reading recent log entries alongside your current staged diff to produce consistent commit messages.

Do I need to stage changes before generating a conventional commit?▼

Yes, you need to stage changes before generating a conventional commit because the Skill specifically inspects staged diffs via git commands to analyze modifications.