aif-commit

Generate conventional commit messages from staged git changes.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/afterwork/arra-aif --skill aif-commit-afterwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/afterwork/arra-aif/tree/main/.cursor/skills/aif-commit
Command: npx skills add https://github.com/afterwork/arra-aif --skill aif-commit-afterwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate conventional commit messages from staged changes to enforce standardized commits and improve changelogs.

Core Features & Use Cases

  • Analyze git diff and staged changes to infer the proper Conventional Commit type
  • Interactively confirm or adjust the generated message before committing
  • Enforce project-specific context and rules via skill-context overrides when present
  • Support splitting large changes into multiple commits when needed

Quick Start

Stage changes with git, then run the aif-commit workflow to generate and apply 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 automatically generate conventional commit messages from staged changes?

You can automatically generate conventional commit messages by running a workflow that analyzes your git diff to infer the correct type, then interactively prompts you to confirm or adjust the message before committing.

What is the conventional commits format and when do I need it for my git workflow?

The conventional commits format standardizes commit messages with structured types to improve changelogs and release notes. You need it when you want consistent commit history across your codebase and pull requests.

Can I split large staged changes into multiple conventional commits?

Yes, you can split large staged changes into multiple commits when needed. The workflow analyzes the git diff and supports breaking down complex changes into separate, properly typed conventional commit messages.

How do I enforce project-specific commit rules when generating conventional commits?

You can enforce project-specific commit rules by using skill-context overrides. When present, the workflow detects these context rules and applies them to the generated conventional commit messages automatically.

Does this conventional commit generator work with existing git CLI workflows?

Yes, it integrates directly with existing git CLI workflows. You stage your changes using standard git commands, then run the workflow to analyze the diff and generate a conventional commit message for confirmation.

Why should I use automated conventional commits instead of writing commit messages manually?

Automated conventional commits eliminate human error and inconsistency by analyzing your git diff to infer the correct type. This enforces standardized commits across your codebase, which improves changelogs and release notes automatically.