commit

Generate Conventional Commits messages from staged git changes.

Updated May 7, 2025
One-click install
npx skills add https://github.com/Alquimia-ai/fair-forge --skill commit-alquimia-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Alquimia-ai/fair-forge/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Alquimia-ai/fair-forge --skill commit-alquimia-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create git commits following Conventional Commits format. Analyzes staged changes and generates properly formatted commit messages.

Core Features & Use Cases

  • Automates generation of conventional commit messages from staged diffs
  • Enforces commit type, scope, and description per Conventional Commits spec
  • Supports team workflows and changelog generation through standardized messages

Quick Start

Run /commit to generate a properly formatted Conventional Commits message from your staged changes.

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 from staged git changes?

Generate conventional commit messages by running /commit in a git working tree to read staged diffs and parse types and scopes. This produces messages that conform to the Conventional Commits specification.

What is the Conventional Commits format for git history?

Conventional Commits format standardizes feature, fix, docs, and chore commits by enforcing a commit type, scope, and description. This maintains a clean history and supports team workflows and changelog generation.

Does this commit message automation work with my existing git working tree?

Yes, this automation works with your existing git working tree. It requires access to the git working tree to read diffs and staged changes before parsing types and scopes to produce conforming messages.

Can I automate conventional commits across team workflows?

You can automate conventional commits across team workflows to standardize feature, fix, docs, and chore commits. This maintains a clean history and supports changelog generation through standardized messages.

What's the best way to enforce commit type and scope in git?

Enforce commit type and scope by automating generation of conventional git commit messages from staged changes. This analyzes staged diffs and enforces type, scope, and description per the Conventional Commits spec.