git-commit

Generate conventional commit messages by analyzing Git diffs.

Updated Nov 16, 2022
One-click install
npx skills add https://github.com/kos3nz/dotfiles --skill git-commit-kos3nz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/kos3nz/dotfiles/tree/main/.config/agents/skills/git-commit
Command: npx skills add https://github.com/kos3nz/dotfiles --skill git-commit-kos3nz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits standardize git history by analyzing code changes and generating semantic commit messages to replace manual drafting and reduce human error.

Core Features & Use Cases

  • Analyze diffs to infer type and scope according to the Conventional Commits spec.
  • Auto-generate commit messages or support interactive overrides for type, scope, and description.
  • Safely stage changes to group logical updates and produce concise messages.

Quick Start

Request a conventional commit message for the current diff.

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

To generate conventional commit messages from git diffs, the Skill analyzes your code changes to infer the semantic type, scope, and description, outputting a ready-to-run git commit command that follows the Conventional Commits spec.

What is a conventional commit and how does diff analysis determine the type and scope?

A conventional commit is a standardized semantic git history message. Diff analysis determines the type and scope by parsing your code changes to identify whether they represent features, fixes, docs, or refactors, replacing manual drafting and reducing human error.

Can I generate a commit message from unstaged changes or do I need to stage them first?

You can generate a commit message with or without staged changes. The Skill safely stages changes to group logical updates, ensuring concise conventional commit messages are produced from your current repository diff.

What's the best way to automate a git workflow to group logical updates before committing?

The best way to automate a git workflow for logical updates is to use diff analysis that safely stages related code changes together, producing concise conventional commit messages that accurately reflect the grouped semantic updates.

Does this conventional commit generator support interactive overrides for the commit type and description?

Yes, the conventional commit generator supports interactive overrides. After analyzing the diff to auto-generate a commit message, you can manually override the inferred type, scope, and description to ensure the output meets your specific needs.