aif-commit

Generate conventional commit messages from staged Git changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages are often inconsistent and time-consuming to craft; this skill automatically generates conventional commit messages from the current Git index, ensuring standard prefixes, scopes, and descriptions.

Core Features & Use Cases

  • Generate conventional commit messages from staged changes in Git.
  • Enforce the Conventional Commits syntax and support project-specific overrides via .ai-factory rules.
  • Assist in maintaining an auditable VCS history across team workflows with automatic messaging and optional context.

Quick Start

Stage your changes and run the aif-commit workflow to generate a conventional commit message.

Frequently Asked Questions about aif-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 changes, this skill reads the Git index, applies project-specific rules, and outputs a ready-to-use message enforcing Conventional Commits syntax with appropriate prefixes and scopes.

What are conventional commits and why use them for Git version control?

Conventional commits standardize Git version-control history by enforcing specific syntax for prefixes, scopes, and descriptions, ensuring consistent and auditable commit messaging across team workflows during development.

How do I automate commit message creation for my Git workflow?

You can automate commit message creation by staging your changes in Git and running this workflow, which reads the diff to automatically generate a properly formatted conventional commit message.

Can I use custom project-specific rules to override generated commit messages?

Yes, you can enforce project-specific overrides by defining .ai-factory rules, which the skill applies when generating the conventional commit message from your staged Git changes.

Does this commit generation skill work with unstaged changes in my repository?

No, this skill specifically processes staged changes by reading the Git index, so you must stage your file modifications before running the workflow to generate an accurate conventional commit message.