aif-commit

Generate conventional commit messages from staged git changes.

Updated Aug 4, 2025
One-click install
npx skills add https://github.com/Svarog83/php-log-monitor --skill aif-commit-svarog83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/Svarog83/php-log-monitor/tree/main/.cursor/skills/aif-commit
Command: npx skills add https://github.com/Svarog83/php-log-monitor --skill aif-commit-svarog83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages from staged changes streamline code review and changelog generation, enforcing consistency.

Core Features & Use Cases

  • Analyze staged changes to propose a compliant commit message.
  • Infer scope from paths or explicit input, and format the message accordingly.
  • Support optional body and footer content per Conventional Commits guidance.

Quick Start

Stage your changes with git add, then run the commit generator to produce 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?

Generating conventional commit messages from staged changes requires analyzing the diff to infer the type, scope, and subject. The tool formats multi-file updates into a compliant message, enforcing subject length and structural rules.

Can conventional commits infer scope automatically from file paths?

Conventional commits can infer scope automatically from file paths or accept explicit input. This ensures the scope accurately reflects the affected component, maintaining consistency across single or multi-file staged changes.

What is the best way to format multi-file staged changes for conventional commits?

The best way to format multi-file staged changes is to analyze the diffs collectively, determine a unified scope, and generate a single conventional commit message. This enforces formatting rules and supports optional body and footer content.

Does this conventional commit generator support optional body and footer content?

Yes, the conventional commit generator supports optional body and footer content per Conventional Commits guidance. This allows you to include additional context, breaking changes, or issue references alongside the staged changes.

Can I automatically push after creating a conventional commit?

You can automatically push after creating a conventional commit if requested. The tool coordinates post-commit actions, generating the message from staged changes and then executing the push to update the remote repository.

Why use conventional commits for staged changes instead of manual messages?

Conventional commits streamline code review and changelog generation by enforcing consistency. Using automated message generation from staged changes prevents formatting errors and ensures scope and type rules are strictly followed.