commit

Generate Conventional Commits 1.0.0 compliant Git commit messages from staged and unstaged changes.

55|4|Updated Dec 27, 2025

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of Git commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's commit history.

Core Features & Use Cases

Automated Commit Message Generation: Creates commit messages based on code changes and user prompts.
Conventional Commits Compliance: Enforces a standardized format for types, scopes, descriptions, and footers.
Use Case: After implementing a new feature, you can ask the AI to generate a feat: commit message, and it will analyze the changes, suggest a type and scope, and format it correctly.

Quick Start

Use the commit skill to generate a conventional commit message for the 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 conventional commit messages for git changes?▼

To generate conventional commit messages, this Skill analyzes your staged and unstaged git changes using `git status` and `git diff` to automatically determine the commit type, scope, and description.

What is the conventional commits format for breaking changes?▼

The conventional commits format for breaking changes uses an exclamation mark `!` after the type or scope, or includes a `BREAKING CHANGE:` footer in the commit message body to clearly indicate the modification.

Can I use this to create specific git commit types like feat or fix?▼

Yes, you can create specific git commit types. The Skill supports standard conventional commit types including `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, and `chore` based on your code changes.

How does automated commit message generation analyze code diffs?▼

Automated commit message generation analyzes code diffs by running `git status` and `git diff` to inspect your staged and unstaged changes, then inferring the appropriate conventional commit type and scope from the detected modifications.

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

You should stage files before generating a conventional commit. The Skill analyzes both staged and unstaged changes using `git status` and `git diff` to accurately formulate the commit type, scope, and description.

Why use conventional commits instead of freeform git commit messages?▼

Using conventional commits instead of freeform git messages enforces a standardized format for types and scopes, which solves the problem of inconsistent commit history and improves project clarity and automated changelog generation.