ai-factory.commit

Generate conventional commit messages from staged Git changes.

1.1k|92|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lee-to/ai-factory --skill ai-factory-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-factory.commit
Source: https://github.com/lee-to/ai-factory/tree/main/skills/commit
Command: npx skills add https://github.com/lee-to/ai-factory --skill ai-factory-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional Commit Generator helps teams keep a clean, predictable Git history by automatically producing standardized commit messages from staged changes.

Core Features & Use Cases

  • Analyze changes with git status and git diff to determine what changed
  • Determine the commit type and optional scope from changed files or user input
  • Enforce subject length and imperative mood; provide body/footers as needed
  • Support common use cases such as small fixes, feature additions, docs updates

Quick Start

Stage changes and invoke the commit skill to generate a conventional commit message.

Frequently Asked Questions about ai-factory.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, stage your changes and invoke the commit skill. It analyzes git status and git diff to determine the type, scope, and subject for your conventional commit automatically.

What is the best way to enforce subject length and imperative mood in git commits?

The best way to enforce subject length and imperative mood is to use a conventional commit generator. It analyzes your staged changes and applies formatting rules to produce a compliant conventional commit message.

Can I automatically determine the commit type and scope from changed files?

Yes, you can automatically determine the commit type and optional scope from changed files. The skill analyzes your git diff to infer the appropriate conventional commit type and scope based on the modifications.

Do I need to manually stage changes before generating a conventional commit message?

Yes, you need to stage changes before generating a conventional commit message. The skill analyzes the staged changes using git status and git diff to produce the correctly formatted commit output.

Does this conventional commit generator support body and footers for complex commits?

Yes, this conventional commit generator supports body and footers. It enforces subject length and imperative mood while providing the necessary body and footer formatting required for complex conventional commits.