aif-commit

Analyze staged git changes to generate Conventional Commits messages.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-commit-exsydev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/ExsyDev/eye-blinking/tree/main/.claude/skills/aif-commit
Command: npx skills add https://github.com/ExsyDev/eye-blinking --skill aif-commit-exsydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages standardize history for readability and automation. This Skill analyzes staged changes to produce a compliant conventional commit message that adheres to the Conventional Commits specification.

Core Features & Use Cases

  • Generate semantic commit messages from the current git diff and staged changes
  • Enforce the Conventional Commits structure for type, scope, and description
  • Integrate with project-specific rules via skill-context overrides to tailor messages

Quick Start

Stage changes with git add, then invoke this skill 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, stage your files with git add, then invoke the skill to analyze the git diff and produce a compliant commit message automatically.

What is the Conventional Commits specification for version control?

The Conventional Commits specification standardizes commit history by enforcing a structured format for commit type, scope, and description, which improves readability and enables workflow automation across a repository.

Can I apply project-specific rules to automated commit messages?

Yes, you can apply project-specific rules to automated commit messages by using skill-context overrides to tailor the generated type, scope, and formatting to your repository's requirements.

How do I validate commit type and scope before finalizing a git commit?

The skill validates the commit type, scope, and formatting by inspecting git status and diffs against the Conventional Commits specification, ensuring the generated message is correctly structured before presenting the result.

Does this workflow automation tool inspect unstaged changes in the git diff?

No, this workflow automation specifically analyzes staged changes to generate the commit message, requiring you to explicitly stage desired file modifications with git add before generating the result.