git-commit

Analyze git diffs to create Conventional Commits messages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Hanseooo/hanseo-opencode-workflows --skill git-commit-hanseooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Hanseooo/hanseo-opencode-workflows/tree/main/skills/git-commit
Command: npx skills add https://github.com/Hanseooo/hanseo-opencode-workflows --skill git-commit-hanseooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized, semantic git commits using the Conventional Commits specification. It analyzes the actual diff to determine the appropriate type, scope, and message, reducing human error and improving traceability.

Core Features & Use Cases

  • Analyze diffs to auto-detect type, scope, and description for commits.
  • Interactive commit with optional type/scope/description overrides.
  • Intelligent file staging to group changes logically and ensure safe commits.

Quick Start

Analyze diffs, stage as needed, and commit with a conventional 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 a git diff?

To generate conventional commits automatically, this tool analyzes your actual git diff to detect the appropriate type, scope, and description, reducing human error and standardizing your version-control workflow.

Can I override the auto-detected type and scope during an interactive commit?

Yes, you can override the auto-detected type, scope, and description during an interactive commit, allowing you to manually adjust the semantic message while still following the Conventional Commits specification.

How do I safely stage files to group code changes logically before committing?

You can safely stage files for logical grouping by using the intelligent file staging feature, which analyzes your changes and ensures only the intended modifications are included in a safe, semantic commit.

Do I need local Git tooling to automate commit management with conventional commits?

Yes, local Git tooling is required to automate commit management, as the diff analysis and staging operations depend on interacting directly with your local version-control repository.

What is the best way to ensure my staged changes follow the Conventional Commits specification?

The best way to ensure staged changes follow the specification is by analyzing the diff to auto-detect the semantic type and scope, which improves traceability and reduces manual formatting errors in version-control.