git-commit

Analyze diffs to create conventional git commits with type and scope.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill git-commit-almazom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/almazom/agents_slash_skills/tree/main/git-commit
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill git-commit-almazom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional git workflows rely on ad-hoc commit messages and manual staging, which can lead to inconsistent history and missed intent. This Skill automates the creation of conventional commits by analyzing diffs, suggesting a type and scope, and staging changes in a way that yields clean, meaningful history.

Core Features & Use Cases

  • Analyze diffs to determine appropriate type and scope for a commit.
  • Generate conventional commit messages that adhere to the Conventional Commits spec.
  • Interactive prompts to override type/scope/description when needed.
  • Intelligent staging to group related changes for a single logical commit.

Quick Start

Ask it to analyze your current changes, propose a conventional type and scope, and commit with an appropriate message.

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 git diffs?

You can automate conventional commits by analyzing git diffs to determine the type, scope, and description. This process evaluates staged or unstaged changes and generates messages adhering to the Conventional Commits spec.

Can I override the suggested commit type and scope during staging?

Yes, interactive prompts allow you to override the type, scope, and description when needed. This ensures you can manually adjust the semantic commit metadata while still automating the diff analysis.

Does this conventional commits tool handle both staged and unstaged changes?

Yes, the tool analyzes both staged and unstaged repository changes. It intelligently groups related changes during staging to create a single logical commit with a meaningful history.

What is the best way to group related git changes into a single logical commit?

Intelligent staging groups related file changes together based on diff analysis. This automated grouping ensures that feature, fix, docs, or refactor changes form a single logical commit.

Do I need repository access to generate semantic commit messages?

Yes, repository access, diff data, and commit execution capability are required. The tool validates your changes against Conventional Commits rules and needs execution permissions to finalize the commit.