commit

Generate conventional commit messages from staged Git changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/srednoff888-art/4 --skill commit-srednoff888-art
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/srednoff888-art/4/tree/main/examples/skills/commit
Command: npx skills add https://github.com/srednoff888-art/4 --skill commit-srednoff888-art

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate conventional commit messages for staged changes.

Core Features & Use Cases

  • Automatically derives a conventional commit format from git diff --cached
  • Supports types: feat, fix, docs, style, refactor, perf, test, chore
  • Provides examples demonstrating proper subject, optional body, and footer formatting
  • Helps maintain a clean, scannable project history across teams

Quick Start

Run git diff --cached to inspect staged changes, then generate a conventional commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged changes?

To generate conventional commit messages for staged changes, the Skill analyzes your git diff --cached output and formats it into a structured <type>(<scope>): <subject> message with optional body and footer.

What commit types are supported by conventional commits automation?

Conventional commits automation supports standard types including feat, fix, docs, style, refactor, perf, test, and chore to categorize staged changes across features, fixes, and maintenance tasks.

Do I need to manually run git diff --cached before generating a commit message?

You need staged changes in your Git workflow before generating a commit message, which requires running git diff --cached to inspect the staged changes the automation will analyze.

Does conventional commit generation include body and footer formatting?

Conventional commit generation includes proper subject, optional body, and footer formatting, providing examples to maintain a clean, scannable project history across teams.

Why use conventional commits for standardizing Git workflow messages?

Using conventional commits standardizes messages across features, fixes, docs, and maintenance tasks, helping maintain a clean, scannable project history across teams.

Can I apply conventional commit format to staged changes across different maintenance tasks?

You can apply conventional commit format to staged changes across various maintenance tasks, ensuring messages are standardized for features, fixes, docs, and chores within Git workflows.