git-commit

Generate conventional commit messages from diffs with type and scope inference.

4|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Tresillo2017/zephyron --skill git-commit-tresillo2017
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Tresillo2017/zephyron/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/Tresillo2017/zephyron --skill git-commit-tresillo2017

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes Git commit messages by analyzing changes and generating conventional commits, reducing ambiguity and manual effort.

Core Features & Use Cases

  • Analyze the actual diff to infer type, scope, and description for commits.
  • Support interactive staging and overrides for type/scope/description before commit.
  • Enforce Conventional Commits format, including breaking-change notation and structured bodies.

Quick Start

Ask the system to generate a conventional commit message from the staged changes 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 a diff?

To generate conventional commit messages from a diff, this Skill analyzes staged changes to infer the type, scope, and description, ensuring the output conforms to the Conventional Commits format without manual effort.

What is the conventional commits format and how does it standardize git history?

The conventional commits format standardizes git history by structuring commit messages with explicit types, scopes, descriptions, and breaking-change notations, reducing ambiguity across software projects and CI pipelines.

Can I override the inferred type or scope before committing changes?

Yes, you can override the inferred type, scope, and description before committing. The Skill supports interactive staging and optional overrides to ensure the generated commit message matches your intent.

Does this git commit automation work in CI pipelines or just local development?

This git commit automation works across both local development and CI pipelines. It analyzes diffs and generates standardized conventional commit messages wherever code changes occur.

How do I indicate breaking changes in automated conventional commits?

To indicate breaking changes in automated conventional commits, the Skill supports breaking-change notation natively. It analyzes the diff and structures the commit message body to highlight breaking changes according to the format.