git-commit-message

Name: git-commit-message
Availability: InStock
Author: Sulhi

Generate conventional commit messages from git diffs and staged changes.

Updated Nov 17, 2025

Search Tags:#git #commit messages #conventional-commits #diff-analysis #scopes #tiered-format

Ready to run

npx skills add https://github.com/sulhicmz/malnu-backend --skill git-commit-message

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-message
Source: https://github.com/sulhicmz/malnu-backend/tree/main/.opencode/skills/vasilyu1983-ai-agents-public-git-commit-message
Command: npx skills add https://github.com/sulhicmz/malnu-backend --skill git-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically generates conventional commit messages from git diffs and staged changes, ensuring consistency and adherence to the Conventional Commits specification.

Core Features & Use Cases

Diff analysis & classification: inspects staged changes to determine type, scope, and impact.
Tiered commit messages: delivers Tier 1 (critical), Tier 2 (standard), or Tier 3 (minor) formats with a primary suggestion and alternatives.
Scope inference: suggests appropriate scopes based on file paths and project structure.
Use Case: when preparing a release or cleanup commit, use this Skill to produce clean, standardized messages.

Quick Start

Use the git-commit-message skill to generate a commit message from the current staged changes.

Frequently Asked Questions about git-commit-message

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

FAQPage Schema

How do I generate conventional commit messages from git diffs?▼

This Skill generates conventional commit messages by analyzing staged git diffs to determine type, scope, and impact, then applies a tiered formatting system to output primary and alternative message suggestions for standardized workflows.

What is a tiered commit message format and when do I need it?▼

A tiered commit message format categorizes changes into Tier 1 critical, Tier 2 standard, or Tier 3 minor levels. You need it for release or cleanup commits to ensure clean, standardized Git workflows with appropriate impact indication.

Can I automatically infer commit scopes from file paths?▼

Yes, you can automatically infer commit scopes from file paths. This Skill inspects your project structure and file paths during diff analysis to suggest appropriate scopes for your conventional commit messages.

Does this work with staged changes only or all unstaged diffs?▼

This Skill analyzes staged git changes to generate conventional commit messages. It inspects the staged diffs to determine type, scope, and impact, ensuring the output matches exactly what you are preparing to commit.

What's the best way to standardize Git workflows for release commits?▼

The best way to standardize Git workflows for release commits is to automatically generate conventional commit messages from diffs. This ensures consistency by applying a tiered formatting system that delivers primary and alternative message suggestions.