commit

Generate conventional git commit messages from staged changes.

1|Updated Jan 30, 2026

Search Tags:#automation #git #workflow #changelog #commit #standardization #conventional

Ready to run

npx skills add https://github.com/PanJason/Awesome_SDE_Skills --skill commit-panjason

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/PanJason/Awesome_SDE_Skills/tree/main/Common/git-commit
Command: npx skills add https://github.com/PanJason/Awesome_SDE_Skills --skill commit-panjason

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating consistent, well-formed git commits is time-consuming and error-prone; this skill automates the generation of conventional commits to improve changelogs and reviews.

Core Features & Use Cases

Generate conventional commit messages (feat, fix, docs, etc.) from staged changes.
Enforce the standard format <type>(<scope>): <description> with optional body and footers.
Integrate into CI pipelines to ensure commit message consistency across the team.

Quick Start

Stage your changes and run /commit to generate a conventional commit message.

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 automatically from staged changes?▼

You can generate conventional commit messages by staging your git changes and running the automation command. It parses the staged diff to output a standardized <type>(<scope>): <description> format.

How do I enforce standard git commit formats like feat and fix across my team?▼

To enforce standard git commit formats, integrate this automation into your CI pipelines. It ensures commit history consistency by requiring structured messages with types like feat, fix, docs, and refactor.

What is the conventional commits format for structuring a git commit message?▼

The conventional commits format structures messages as <type>(<scope>): <description>, with optional body and footers. Supported types include feat, fix, docs, style, refactor, test, and chore.

Can I include a body and footers when automating conventional commits?▼

Yes, conventional commits support an optional body and footers alongside the required header. The automation generates these elements from your staged changes to provide detailed context.

Why use conventional commits for software development workflows?▼

Using conventional commits creates an easily parsable commit history, which improves changelog generation and code reviews. It standardizes features, fixes, and maintenance tasks across the project.