git-commit

Generate conventional git commits with enforced types and subject limits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/edri2or/project-life-132 --skill git-commit-edri2or
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/edri2or/project-life-132/tree/main/exported-skills/git-commit
Command: npx skills add https://github.com/edri2or/project-life-132 --skill git-commit-edri2or

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits provide a predictable, machine-readable history that improves changelogs, release notes, and code reviews by standardizing message formats.

Core Features & Use Cases

  • Enforces standard commit types (feat, fix, docs, style, refactor, test, chore, ci, perf).
  • Validates subject line length (<= 72 characters) and imperative mood.
  • Guides users to craft an optional body and ensures messages are ready for release automation.
  • Integrates with common Git workflows (status, diff, add, commit, push) to streamline commits.

Quick Start

Tell your AI assistant to format your next set of changes into a conventional commit with a concise subject and optional body.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write conventional commits for git feature branches?

To write conventional commits, format messages using standard types like feat, fix, or refactor with an imperative mood subject line under 72 characters. This standardizes git histories for better changelogs and automated release notes across feature branches.

What is the maximum subject line length for a conventional commit?

The maximum subject line length for a conventional commit is 72 characters. Keeping subject lines concise and in imperative mood ensures messages are machine-readable and ready for release automation workflows.

What conventional commit types should I use for code changes?

Use conventional commit types feat, fix, docs, style, refactor, test, chore, ci, or perf for code changes. Each type categorizes your git history to improve code reviews and generate predictable, machine-readable changelogs.

Does this conventional commit workflow guide git status, diff, and push?

Yes, this conventional commit workflow guides you through standard git operations including status, diff, add, commit, and push. It integrates these steps to streamline local git workflows during code changes and reviews.

Can I add a body to my conventional commit message?

Yes, you can add an optional body to your conventional commit message. After enforcing a concise subject line and imperative mood, the workflow guides you to craft a detailed body to provide additional context for code reviews.