skills.rest
MGurtD
MGurtDCOMMUNITY
Explore all skills by this author →
𝕏@marcgurtGitHub

git-commits

Generate conventional commit messages with type, scope, and description.

2|1|Updated Feb 16, 2026
Search Tags:#git#commits#types#version-control#conventional#scopes
One-click install
npx skills add https://github.com/MGurtD/lilith --skill git-commits-mgurtd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commits
Source: https://github.com/MGurtD/lilith/tree/main/.github/skills/git-commits
Command: npx skills add https://github.com/MGurtD/lilith --skill git-commits-mgurtd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafting consistent conventional commit messages is error-prone and slows development. This skill helps by formatting user input into standardized messages for all commits.

Core Features & Use Cases

  • Conventional format enforcement: Generates messages in the form type(scope): description and enforces a 72-character subject limit.
  • Scope and type guidance: Suggests appropriate scopes (backend, frontend, docs) and types (feat, fix, docs, refactor, perf, test, chore).
  • Use Case: When preparing commits for code reviews or automated changelogs, ensuring consistency across the project.

Quick Start

Describe your change and I will produce a conventional commit message in the proper format.

Frequently Asked Questions about git-commits

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

FAQPage Schema
How do I generate conventional commit messages automatically?▼

You can generate conventional commit messages automatically by inputting a plain-text description of your changes. The skill formats it into the standard type(scope): description structure, enforcing a 72-character subject limit for version control consistency.

What types and scopes are used in conventional commits?▼

Common types include feat, fix, docs, refactor, perf, test, and chore, while suggested scopes cover backend, frontend, and docs. These options categorize changes for automated changelogs and code reviews.

How do I format git commits for automated changelogs and code reviews?▼

To format git commits for automated changelogs, use the conventional structure type(scope): description. This standardization ensures consistency across backend and frontend modules during releases.

Does this conventional commit generator enforce subject length and punctuation limits?▼

Yes, this conventional commit generator enforces a strict 72-character subject length limit and validates punctuation. This ensures your version-control history remains clean and compliant.

When do I need to use conventional commit formatting?▼

You need conventional commit formatting when preparing changes for code reviews or automated release changelogs. It ensures standardized messaging across all backend and frontend project modules.

What is the best way to ensure consistent git commit messages across a project?▼

The best way to ensure consistent git commit messages is to enforce the conventional commit structure type(scope): description. This standardizes scopes and types across all developer contributions.

Related Skills

Explore More Software Engineering Skills→
christopherlouetchristopherlouet
5

work-commit

Generate Conventional Commits commit messages from git diff outputs.

Community
Basic
sobhanashinesobhanashine
1

commit-style

Generates Conventional Commit messages with type, scope, and subject.

Community
Basic
BaGyun0107BaGyun0107

commit

Generate Conventional Commits messages from code diffs.

Community
Basic
zhengfranzhengfran

conventional-commit

Generate Conventional Commit messages in the type(scope): description format.

Community
Basic