git-commit

Generate conventional commit messages from git diffs.

Updated Aug 27, 2026

Search Tags:#automation #git #commit #staging #diff #messages #conventional-commits

Ready to run

npx skills add https://github.com/shuretokki/void --skill git-commit-shuretokki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/shuretokki/void/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/shuretokki/void --skill git-commit-shuretokki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate standardized, semantic git commits by analyzing diffs to suggest type, scope, and description, reducing manual effort and improving history clarity.

Core Features & Use Cases

Analyze diffs to determine conventional commit type, scope, and description.
Propose and format commits that follow the Conventional Commits specification.
Use during feature development or code reviews to streamline commit messages.

Quick Start

Generate a conventional commit message from the current diff and apply it to the 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 conventional commit messages from a git diff?▼

You can generate conventional commit messages from a git diff by analyzing the staged changes to extract the type, scope, and description. This automation standardizes commit history during feature development or code reviews.

Can I override the suggested conventional commit type and scope?▼

Yes, you can override the suggested conventional commit type and scope. The process proposes a commit message from the diff and supports interactive overrides to ensure the final message meets your specific formatting needs.

What is the best way to standardize git commit history for a new feature?▼

The best way to standardize git commit history is to automate conventional commit creation from code diffs. This ensures every commit includes a semantic type, scope, and description without manual formatting effort.

Does this conventional commit automation work without external dependencies?▼

Yes, this conventional commit automation works without external dependencies. It independently analyzes diffs and formats messages according to the Conventional Commits specification without requiring additional tools or libraries.

When do I need to use conventional commits during code reviews?▼

You need to use conventional commits during code reviews to standardize commit history clarity. Analyzing diffs to propose semantic commit messages streamlines the review process and maintains consistent formatting across feature development.