skills.rest
IKatsuba
IKatsubaCOMMUNITY
Explore all skills by this author →
Website𝕏@katsuba_igorGitHub

git:commit

Generate Conventional Commits messages for staged Git changes.

1|Updated Jan 21, 2026
Search Tags:#automation#git#commit#prompting#commit-message#conventional-commits#scopes
One-click install
npx skills add https://github.com/IKatsuba/skills --skill git-commit-ikatsuba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git:commit
Source: https://github.com/IKatsuba/skills/tree/main/git/commit
Command: npx skills add https://github.com/IKatsuba/skills --skill git-commit-ikatsuba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers craft precise, conventional commit messages automatically, reducing cognitive load and ensuring consistency across the codebase.

Core Features & Use Cases

  • Auto-detect commit type: Detects the appropriate type (feat, fix, chore, docs, etc.) from changes.
  • Prompt-driven selection: If ambiguity exists, prompts user to pick the commit type.
  • Structured messages: Generates messages following Conventional Commits format with optional scope.

Quick Start

Run the git:commit skill to automatically detect a commit type and generate a conventional commit message for your 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 automatically generate a conventional commit message for staged Git changes?▼

You can automatically generate a conventional commit message by running the git:commit skill against your staged Git changes. It detects the appropriate commit type from the diff and structures the message according to the Conventional Commits specification.

How does automatic commit type detection work for conventional commits?▼

Automatic commit type detection works by analyzing your staged Git changes to identify whether they represent a feature, bug fix, or maintenance task. If the change type is ambiguous, the skill prompts you to manually select the correct conventional commit type.

Can I include a scope in my conventional commit messages automatically?▼

Yes, you can include an optional scope in your conventional commit messages. The skill generates structured messages that conform to the Conventional Commits specification and supports adding scopes to categorize your changes more precisely.

What is the best way to enforce consistent conventional commits across a large repository?▼

To enforce consistent conventional commits across a large repository, use an automated skill like git:commit. It reduces cognitive load by prompting for ambiguous types and automatically structuring messages, ensuring uniformity across feature development and bug fixes.

Do I need to manually specify the commit type every time I create a conventional commit?▼

No, you do not need to manually specify the commit type every time. The skill auto-detects the type from your staged changes and only prompts you for selection when there is ambiguity in the nature of the Git changes.

Related Skills

Explore More Software Engineering Skills→
yoshihiko555yoshihiko555

commit

Stage and commit only files discussed in the conversation.

Community
Advanced
shellicarshellicar

github-release

Create GitHub releases from version tags to trigger npm-publish workflows.

Community
Advanced
deepklaritydeepklarity
87

dk-merge-resolve

Diagnose git merge, rebase, cherry-pick, or stash pop conflicts and guide resolution.

Official
Advanced
gaebalaigaebalai
2

release-tag-plan

Plan release tagging and CHANGELOG strategy using semantic versioning.

Community
Advanced