aif-commit

Generate conventional commit messages from staged git changes.

56|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/lee-to/ai-workspace --skill aif-commit-lee-to
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/lee-to/ai-workspace/tree/main/.claude/skills/aif-commit
Command: npx skills add https://github.com/lee-to/ai-workspace --skill aif-commit-lee-to

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messaging for staged changes, reducing manual effort and ensuring consistent project history.

Core Features & Use Cases

  • Analyze staged diffs to determine an appropriate conventional commit type (feat, fix, docs, style, refactor, perf, test, build, ci, chore).
  • Enforce the Conventional Commits specification and apply project-specific skill-context overrides.
  • Guide users through a deterministic commit workflow, prompting for scope, subject, and body as needed.

Quick Start

Stage changes and run the aif-commit 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 automatically from staged git changes?

To generate conventional commit messages automatically, you can use automation tools that analyze your staged git diffs to determine the appropriate commit type, scope, and subject. This enforces the Conventional Commits specification and ensures consistent project history.

What is the conventional commit workflow for ensuring commit message quality?

The conventional commit workflow for ensuring commit message quality involves analyzing staged changes, applying the Conventional Commits specification, and guiding the user through a structured process prompting for scope, subject, and body as needed.

Can I apply project-specific rules when generating conventional commits?

Yes, you can apply project-specific rules when generating conventional commits by integrating skill-context overrides. These rules are enforced alongside the standard Conventional Commits specification during the automated commit generation process.

Does this automated commit workflow work without any dependencies?

Yes, this automated commit workflow works without any dependencies. It operates independently to analyze your staged git changes and guide you through a deterministic, gated commit workflow without requiring external components.

How do I determine the correct conventional commit type for my git diff?

To determine the correct conventional commit type for your git diff, automation tools analyze the staged changes and categorize them into types like feat, fix, docs, style, refactor, perf, test, build, ci, or chore based on the modifications.

What is the best way to automate conventional commit formatting for staged changes?

The best way to automate conventional commit formatting for staged changes is using a deterministic workflow tool that analyzes diffs, applies project-specific context rules, and enforces the Conventional Commits specification to reduce manual effort and ensure quality.