git-commit

Analyze git diffs and stage changes into Conventional Commits messages.

2|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/haotool/app --skill git-commit-haotool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/haotool/app/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/haotool/app --skill git-commit-haotool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of standardized, semantic git commits by analyzing diffs, detecting intent, and staging changes intelligently to ensure a clean project history.

Core Features & Use Cases

  • Auto-detects type and scope from changes and derives a conventional commit message.
  • Intelligent staging that groups related changes for a single commit.
  • Interactive commit with optional type/scope/description overrides and safety checks.

Quick Start

Tell the assistant to commit your changes using a conventional commit, and it will analyze the diff, stage the right files, and generate a compliant message.

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 commits automatically from my git diff?

You can generate conventional commits automatically by analyzing your git diff to detect the type and scope, then deriving a compliant commit message. This ensures standardized project history without manual formatting.

What is the best way to stage related changes for a single semantic commit?

The best way to stage related changes is using intelligent staging that groups associated file modifications together. This ensures a single semantic commit captures all relevant changes cleanly and deterministically.

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

Yes, you can override the auto-detected type and scope during the interactive commit process. This allows you to manually adjust the message, apply safety checks, and ensure the commit matches your intent.

Does automated commit generation work for bugfix and refactor tasks in collaborative Git repositories?

Automated commit generation works across feature, bugfix, and refactor tasks in collaborative Git repositories. It applies to daily development workflows by enforcing the Conventional Commits format for consistent project history.

Why should I use conventional commits instead of manual messages in my daily development workflow?

Conventional commits enforce a semantic format that auto-detects intent from code changes, ensuring a clean project history. This standardizes collaboration and eliminates the inconsistency of manually written commit messages.