ai-factory.commit

Generates standardized commit messages from staged changes and diffs using Conventional Commits format rules.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/YaroslavKomarov/ShedulerBot --skill ai-factory-commit-yaroslavkomarov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-factory.commit
Source: https://github.com/YaroslavKomarov/ShedulerBot/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/YaroslavKomarov/ShedulerBot --skill ai-factory-commit-yaroslavkomarov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create conventional commit messages by analyzing staged changes. This helps teams maintain a clean, standardized commit history and reduces manual effort.

Core Features & Use Cases

  • Analyze staged changes with git to propose a Conventional Commits compliant message
  • Determine scope from file paths or user-provided context to improve traceability
  • Enforce Conventional Commits format rules: type, scope, subject in imperative mood, and optional body content

Quick Start

Stage your changes and ask the AI 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?

Generate conventional commit messages by analyzing staged git changes and diffs to produce standardized semantic messages. The tool reads your staged files to automatically create compliant messages without manual formatting effort.

What format does the generated semantic commit message follow?

The semantic commit message follows the format <type>(<scope>): <subject> with an optional body. It enforces the Conventional Commits specification, uses imperative mood, and restricts the subject length to under 72 characters.

How does scope detection work for conventional commits?

Scope detection for conventional commits works by analyzing file paths from your staged changes or extracting context from user-provided input. This automatically determines the appropriate scope to improve commit traceability across the project.

Can I use this to clean up my git history before pushing to a remote repository?

Yes, you can clean up your git history by generating standardized messages from staged changes before pushing to a remote repository. This enforces a consistent commit history and reduces manual effort for your team.

Do I need any dependencies installed to generate standardized commit messages?

You do not need any specific dependencies installed to generate standardized commit messages. The tool operates independently to analyze your staged changes and create Conventional Commits compliant messages without external requirements.