git-commit

Name: git-commit
Availability: InStock
Author: hiroyukimakita

Generate conventional git commit messages by analyzing code diffs.

Updated Jan 31, 2026

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

Ready to run

npx skills add https://github.com/HiroyukiMakita/dev-kintone-plugin --skill git-commit-hiroyukimakita

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/HiroyukiMakita/dev-kintone-plugin/tree/main/.opencode/skills/git-commit
Command: npx skills add https://github.com/HiroyukiMakita/dev-kintone-plugin --skill git-commit-hiroyukimakita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the git commit process by analyzing code changes, suggesting conventional commit messages, and intelligently staging files, ensuring cleaner and more standardized version control history.

Core Features & Use Cases

Conventional Commits: Automatically generates commit messages adhering to the Conventional Commits specification (e.g., feat:, fix:).
Intelligent Staging: Analyzes diffs to suggest or automatically stage relevant files for a commit.
Message Generation: Creates descriptive commit messages based on code changes, reducing manual effort and improving clarity.
Use Case: After making several changes to a feature and fixing a bug, use this skill to automatically generate a commit message like feat: implement user profile editing, fix: correct avatar upload bug and stage only the relevant files.

Quick Start

Use the git-commit skill to analyze my changes and create a commit message.

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 conventional commit messages from git diffs?▼

You can generate conventional commit messages from git diffs by analyzing code changes to automatically create standardized prefixes like feat: or fix: alongside descriptive commit messages.

Can I automatically stage relevant files based on code changes before committing?▼

Yes, intelligent staging analyzes your code diffs to suggest or automatically stage only the relevant files for your git commit, ensuring a clean and accurate version control history.

What is the best way to write conventional commits for multiple file changes?▼

Writing conventional commits for multiple file changes is best handled by analyzing the combined diffs to generate a single descriptive message that covers features, fixes, and refactors.

Do I need the git CLI installed to use AI commit message generation?▼

Yes, you need the git CLI installed and available in your environment, as the commit message generation requires git CLI access to analyze diffs and stage files.

How does conventional commit analysis handle features, fixes, and refactors?▼

Conventional commit analysis handles features, fixes, and refactors by evaluating the code diff to determine the change type, then applying the correct conventional commit specification for type, scope, and description.