skills.rest
fanthus
fanthusCOMMUNITY
Explore all skills by this author →
GitHub

git-commit-pro

Generate Conventional Commits messages from staged diffs.

Updated Feb 2, 2026
Search Tags:#git#commit#scope#conventional-commits#type#subject#body
One-click install
npx skills add https://github.com/fanthus/agent-skills --skill git-commit-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-pro
Source: https://github.com/fanthus/agent-skills/tree/main/git-commit-pro
Command: npx skills add https://github.com/fanthus/agent-skills --skill git-commit-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious process of crafting consistent and professional commit messages, ensuring teams follow the Conventional Commits standard.

Core Features & Use Cases

  • Conventional commits: Generate messages that conform to feat, fix, docs, style, refactor, test, chore with optional scope.
  • Scope and subject control: Enforce subject length and provide a concise summary; include an optional body for details.
  • Use Case: When you need to commit multiple changes, generate a single, compliant message that accurately describes the changes and can be parsed by changelogs.

Quick Start

When you want to commit changes, provide a brief description and optional scope, and the skill will output a single Conventional Commits line such as feat(auth): add login feature.

Frequently Asked Questions about git-commit-pro

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

FAQPage Schema
How do I generate a conventional commit message automatically?▼

To generate a conventional commit message, provide a brief description and optional scope. The skill analyzes your staged diffs and outputs a formatted single-line message following the Conventional Commits specification.

What is the conventional commits format for a git commit?▼

The conventional commits format structures a git commit as <type>(<scope>): <subject>, followed by an optional body after a blank line. Types include feat, fix, docs, style, refactor, test, and chore.

Can I include a body and scope in my conventional commit?▼

Yes, you can include an optional scope in parentheses and an optional body after a blank line. The subject length is enforced to provide a concise summary of the staged changes.

Does this conventional commits generator work with staged git diffs?▼

Yes, the generator works directly with staged git diffs. It analyzes the changes you have staged and produces a single, compliant commit message that can be parsed by changelogs.

When do I need to use conventional commits for my git history?▼

You need conventional commits when your team requires consistent, professional commit messages that can be automatically parsed to generate changelogs and manage semantic versioning.

Related Skills

Explore More Software Engineering Skills→
rtfpessoartfpessoa

commit

Generate structured git commit messages with titles, motivations, and summaries.

Community
Intermediate
mpazarynampazaryna
1

journal

Generate markdown journal entries from git commit history.

Community
Basic
caseymanoscaseymanos

git-hooks

Configure Husky Git hooks for pre-commit linting, pre-push testing, and commit message validation.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced