git-commit

Analyze diffs to generate conventional commit messages and stage changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/g00hyun/okky-vibe-aaa --skill git-commit-g00hyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/g00hyun/okky-vibe-aaa/tree/main/.agent/skills/git-commit
Command: npx skills add https://github.com/g00hyun/okky-vibe-aaa --skill git-commit-g00hyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating standardized, semantic git commits by analyzing diffs, proposing conventional commit messages, and staging changes intelligently to improve history readability.

Core Features & Use Cases

  • Analyze diff to infer type, scope, and subject according to the Conventional Commits specification.
  • Auto-stage changes for logical grouping and message accuracy.
  • Generate and apply a commit message with optional interactive overrides.

Quick Start

Ask the assistant to commit your current changes using conventional commits with automatic type/scope detection and smart staging.

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 commits with smart staging?

Automating conventional commits with smart staging involves analyzing git diffs to infer the type and scope, intelligently staging related files, and generating a structured commit message. This improves history readability and standardizes semantic versioning.

How do I generate a conventional commit message from a git diff?

Generating a conventional commit message from a git diff requires analyzing the modified code to determine the appropriate type, scope, and subject. The system proposes a standardized message based on the diff content and applies it to the commit.

Can I interactively override the type and scope when generating a commit message?

Yes, you can interactively override the type and scope when generating a commit message. While the system automatically proposes these values by analyzing the diff, you can request interactive prompts to manually adjust the type, scope, or description.

What is the best way to group file changes logically before committing?

The best way to group file changes logically before committing is through intelligent staging. By analyzing diffs, the system auto-stages related modifications to ensure logical grouping and commit message accuracy.

Do I need to manually stage files before requesting an automated git commit?

No, you do not need to manually stage files before requesting an automated git commit. The process applies smart staging by analyzing your diffs and automatically grouping changes to ensure accurate conventional commit messages.