git-commit

Analyze staged diffs and generate conventional git commit messages.

Updated Dec 14, 2025

Search Tags:#automation #git #staging #version-control #conventional-commits #diff-analysis #commit-suggestions

Ready to run

npx skills add https://github.com/louisburroughs/durion --skill git-commit-louisburroughs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of conventional git commits by analyzing diffs and proposing standardized messages.

Core Features & Use Cases

Automatic type/scope inference from diffs to produce a consistent commit subject and optional body.
Interactive overrides for type, scope, and description to tailor messages for reviews or PRs.
Intelligent staging guidance that groups related changes to minimize noisy commits and improve traceability.
Use Case: When preparing a PR with multiple files changed, generate a single coherent conventional commit describing the intent.

Quick Start

Stage the changes you want included in the commit using git add or git add -p. Run the commit flow to apply a conventional commit message, for example: git commit -m "<type>[scope]: <description>"

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate conventional commit messages from staged git diffs?▼

You can automate conventional commit messages by analyzing staged git diffs to automatically infer the type and scope, producing a standardized commit subject and optional body for your version control workflow.

What is the best way to group related file changes for a coherent git commit?▼

Intelligent staging guidance groups related file changes together to minimize noisy commits and improve traceability, ensuring a single coherent conventional commit describes the intent across multiple files.

Can I override the inferred type and scope when generating a conventional commit?▼

Yes, you can use interactive overrides for type, scope, and description to tailor conventional commit messages, allowing you to customize the deterministic formatting for code reviews or pull requests.

Does this approach work with changes staged across multiple files?▼

Yes, the commit generation applies to staged changes across multiple files, analyzing the complete diff to propose a single standardized conventional commit message that describes the overall intent.

How do I start creating conventional commits using diff analysis?▼

Stage the desired changes using git add or git add -p, then run the commit flow to apply a conventional commit message format like <type>[scope]: <description> based on the analyzed diff.