aif-commit

Analyze staged git changes to generate Conventional Commits messages.

83|5|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-commit-artemyurov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/ArtemYurov/TomoBar/tree/main/.claude/skills/aif-commit
Command: npx skills add https://github.com/ArtemYurov/TomoBar --skill aif-commit-artemyurov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafting conventional commit messages by hand is error-prone and slows down collaboration; this skill automates the process by generating standardized messages from your staged changes.

Core Features & Use Cases

  • Analyze git status and diffs to determine the appropriate commit type (feat, fix, docs, etc.) and scope.
  • Enforce the Conventional Commits specification (subject length, formatting, and optional body).
  • Prompt for confirmation before committing and optionally push to the remote repository.

Quick Start

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

To generate conventional commit messages from staged changes, this skill analyzes your git status and diffs to determine the appropriate type, scope, and subject. It then prompts for confirmation before executing the git commit.

What is the best way to enforce the conventional commits specification for features and fixes?

The best way to enforce the conventional commits specification is to use this skill to analyze staged changes and automatically format the subject length and structure for features, fixes, and docs, ensuring strict compliance before committing.

Can I automatically push to a remote repository after creating a conventional commit?

Yes, you can automatically push to a remote repository after creating a conventional commit. The skill performs the git commit and explicitly offers to push your staged changes to the remote repository upon confirmation.

Does this conventional commit generator work for projects of varying sizes and scopes?

Yes, this conventional commit generator works for projects of varying sizes and scopes. It guides users to select the appropriate type, scope, and subject across different modules, ensuring standardized version-control messages.

Why does manually writing conventional commit messages slow down collaboration?

Manually writing conventional commit messages slows down collaboration because it is an error-prone process. Automating the generation of standardized messages from your staged changes eliminates formatting errors and speeds up version-control workflows.

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

Yes, you need to stage your changes before generating a conventional commit message. The skill specifically analyzes your staged changes and their diffs to determine the correct commit type, scope, and subject formatting.