git-commit

Generate conventional git commits by analyzing diffs for type and scope.

Updated Aug 27, 2025
One-click install
npx skills add https://github.com/Andrej1601/HTMLSignage --skill git-commit-andrej1601
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Andrej1601/HTMLSignage/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/Andrej1601/HTMLSignage --skill git-commit-andrej1601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assemble and publish conventional, semantic git commits by analyzing diffs to infer type, scope, and message, reducing manual guesswork during version control.

Core Features & Use Cases

  • Auto-detects the appropriate type (feat, fix, docs, etc.) and scope from a set of changes
  • Generates conventional commit messages aligned with the Conventional Commits spec
  • Supports interactive overrides for type, scope, and description
  • Performs intelligent staging to group related changes into a single commit

Quick Start

Provide a concise, conventional commit message for the currently 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 generate conventional commit messages automatically from git diffs?

This Skill automates conventional commit generation by analyzing your git diffs to infer the type, scope, and description. It applies intelligent staging to group related code changes into a single standardized commit message, reducing manual guesswork during version control.

What's the best way to automate smart staging for related code changes?

Automating smart staging involves analyzing repository changes and grouping related modifications together. This ensures related code changes are assembled into a single conventional commit automatically before publishing.

Can I override the auto-detected type and scope of a conventional commit?

Yes, you can override the auto-detected type, scope, and description. While the tool automatically infers these values from your git diff, it supports interactive overrides to manually adjust the conventional commit parameters before finalizing.

How does conventional commit automation determine the correct commit type from changes?

Conventional commit automation determines the correct type by analyzing the content and context of your code diffs. It infers whether changes represent a feature, fix, or documentation update to align with the Conventional Commits specification.

Do I need any external dependencies to automate version control commits?

No external dependencies are required to automate version control commits. The Skill operates independently with no required dependencies, analyzing staged changes directly to produce semantic conventional commit messages.

When should I not use automated conventional commit generation?

Automated conventional commit generation should be avoided when code changes require complex, highly contextual explanations that defy standard semantic types. In such cases, manual message crafting ensures accurate version control history over automated diff analysis.