git-commit

Generate conventional commit messages by analyzing git diffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers create standardized, semantic git commits by analyzing diffs and generating conventional commit messages, reducing cognitive load and ensuring consistency across a project.

Core Features & Use Cases

  • Conventional Commit Generation: auto-detects type and scope from changes and suggests an appropriate commit message.
  • Interactive Staging & Overrides: allows you to override the type, scope, and description, and group related changes for cohesive commits.
  • Smart Messaging for Workflows: supports typical development workflows, including multiple commits in a single feature branch and clear changelogs.
  • Use Case: When you've modified several files, run this Skill to produce a single conventional commit that describes the feature or fix and its scope.

Quick Start

Stage your changes with git add, then run the git-commit command to create a conventional commit message based on the diff and apply it.

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?

You can generate conventional commit messages automatically by running a tool that analyzes your git diffs to designate the type, scope, and message based on your staged or unstaged changes.

Can I override the auto-generated type and scope for a conventional commit?

Yes, you can override the auto-generated type, scope, and description using an interactive mode, which also allows you to group related files together for more coherent conventional commits.

How do I create coherent conventional commits when I have modified multiple files?

To create coherent conventional commits across multiple modified files, you can use an interactive staging mode to group related changes together before generating the final commit message.

Do I need to stage my changes before generating a conventional commit message?

No, you do not need to stage changes beforehand; the generation process supports both staged and unstaged changes, though you can stage them with git add if preferred.

What is the best way to maintain consistent conventional commits across a feature branch?

The best way to maintain consistent conventional commits is to use an automated tool that analyzes diffs and suggests semantic messages, supporting multiple commits within a single feature branch workflow.

Does this conventional commit generation require a specific environment to run?

Yes, conventional commit generation runs in a Bash environment with git installed, analyzing your file differences to produce messages that adhere to the Conventional Commits specification.