git-commit-conventional

Generate Conventional Commit messages and execute safe Git commits.

2|2|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/liatrio-labs/ai-prompts --skill git-commit-conventional-liatrio-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-conventional
Source: https://github.com/liatrio-labs/ai-prompts/tree/main/skills/git-commit-conventional
Command: npx skills add https://github.com/liatrio-labs/ai-prompts --skill git-commit-conventional-liatrio-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and agents (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Git commits by ensuring adherence to Conventional Commit standards, improving commit history clarity, and integrating pre-commit hooks for automated quality checks.

Core Features & Use Cases

  • Conventional Commit Generation: Automatically generates commit messages following the <type>(<scope>): <subject> format.
  • Commit Splitting Logic: Analyzes changes to suggest or enforce splitting broad changes into smaller, more manageable commits.
  • Pre-commit Hook Integration: Runs configured pre-commit hooks to catch issues before committing.
  • AI Attribution: Includes Co-Authored-By for AI-generated commits without cluttering the message.
  • Use Case: When you've made several unrelated changes, this skill helps you break them down into atomic commits with clear messages, making your Git history a valuable asset.

Quick Start

Use the git-commit-conventional skill to create a commit for your staged changes.

Frequently Asked Questions about git-commit-conventional

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate conventional commit messages from my working tree changes?

To generate conventional commit messages, this skill analyzes your working tree diffs and outputs messages in the `<type>(<scope>): <subject>` format. It evaluates commit pressure and stages changes intentionally before committing.

How do I split broad working tree changes into smaller, atomic git commits?

Splitting broad changes into atomic git commits is handled by the skill's commit splitting logic. It analyzes your diffs and enforces logical separation, suggesting or enforcing smaller, manageable commits to keep your history clear.

Does this conventional commit generator run pre-commit hooks before finalizing the git commit?

Yes, this conventional commit generator runs configured pre-commit hooks before finalizing the git commit. It integrates automated quality checks to catch issues early and ensures safe Git commit execution.

What is the best way to handle AI attribution in automated conventional commits?

The best way to handle AI attribution in automated conventional commits is using the skill's built-in AI attribution policy. It applies `Co-Authored-By` tags cleanly without cluttering the commit message body.

Can I use this skill to plan git commits before executing them on my staged changes?

Yes, you can use this skill to plan git commits before execution. It provides deterministic output contracts for commit planning and previews, allowing you to review staged changes and proposed messages safely.

Why should I enforce logical separation when creating conventional commits?

Enforcing logical separation when creating conventional commits prevents unrelated changes from being grouped together. This practice analyzes your diffs to break down broad changes, making your Git history a valuable asset for code review.