aif-commit

Generates semantic commit messages from staged Git changes using the Conventional Commits specification.

2|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/drsapaev/final --skill aif-commit-drsapaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/drsapaev/final/tree/main/.codex/skills/aif-commit
Command: npx skills add https://github.com/drsapaev/final --skill aif-commit-drsapaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of Git commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's commit history.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes staged changes to suggest a commit type, scope, and subject.
  • Conventional Commits Compliance: Enforces a standardized format for commit messages, improving readability and enabling automated changelog generation.
  • Use Case: After making several code changes, you can invoke this Skill to generate a commit message like feat(auth): implement user registration endpoint without manually recalling the specification.

Quick Start

Use the aif-commit skill to create a commit message for your staged changes.

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 for staged Git changes?

Conventional commits provide a standardized format for Git commit messages by using structured types like feat, fix, or docs, which improves commit history readability and enables automated changelog generation.

Can I include a specific scope in my conventional commit message?

Yes, you can include an optional scope in your conventional commit message to specify the context of your changes, resulting in formats like feat(auth): implement user registration endpoint for better semantic clarity.

What is the best way to automate semantic commit message creation for code changes?

Automating semantic commit message creation involves analyzing staged code changes to determine the correct commit type and subject, eliminating the need to manually recall the conventional commits specification.

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

Yes, you need to stage your Git changes first, because the conventional commit message generation analyzes the staged changes to infer the semantic commit type, scope, and subject accurately.

What commit types are supported when generating conventional commits?

Supported conventional commit types include standard semantic categories such as feat, fix, and docs, allowing you to categorize staged code changes for consistent and readable project history.