git-commit

Generate conventional commit messages from staged changes with type-scope format.

Updated Mar 14, 2026

Search Tags:#automation #git #commit #conventional-commits #diff-analysis #imperative-mood #subject-length

Ready to run

npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill git-commit-captainphantasy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/CaptainPhantasy/floyd-v5/tree/main/extensibility/skills/git/git-commit
Command: npx skills add https://github.com/CaptainPhantasy/floyd-v5 --skill git-commit-captainphantasy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consistent, conventional commit messages from staged changes can be error-prone and time-consuming; this skill automates the process to ensure standardized VCS history.

Core Features & Use Cases

Automatic Conventional Commit Generation: Creates messages following the <type>(<scope>): <description> format based on the staged diff.
Subject and Body Rules: Enforces a subject limited to 50 characters in imperative mood, and provides guidance for the body when applicable.
Use Case: Ideal for feature work, bug fixes, docs updates, and chore tasks in a software engineering workflow.

Quick Start

Stage your changes and run git-commit to generate a conventional commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I generate conventional commit messages from staged git changes?▼

To generate conventional commit messages from staged git changes, you can use an automated diff analysis tool that reads your staged files and applies the correct <type>(<scope>): <description> format. This ensures standardized VCS history without manual formatting.

What is the correct format for a conventional commit subject line?▼

The correct format for a conventional commit subject line is <type>(<scope>): <description>. The subject must be limited to 50 characters, written in imperative mood, and must not end with a trailing period to ensure proper parsing.

Does automated commit generation work for refactoring and documentation updates?▼

Yes, automated commit generation works for refactoring and documentation updates. The diff analysis targets various software engineering workflows, including feature development, bug fixes, docs updates, and chore tasks, applying the appropriate commit type to each.

How do I enforce imperative mood and subject length limits in git commits?▼

To enforce imperative mood and subject length limits in git commits, an automated generation skill validates the staged diff output against strict rules. It restricts the subject to 50 characters and checks verb tense to ensure compliance.

What is the best way to automate conventional commits for software engineering workflows?▼

The best way to automate conventional commits for software engineering workflows is by running a diff analysis tool on staged changes. This automatically enforces formatting rules and generates standardized messages, eliminating manual error-prone formatting.