aif-commit

Generate Conventional Commits messages from staged Git changes.

Updated Feb 23, 2026

Search Tags:#git #developer tools #code review #version control #commit #conventional commits

Ready to run

npx skills add https://github.com/hightemp/process-manager --skill aif-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/hightemp/process-manager/tree/main/.github/skills/aif-commit
Command: npx skills add https://github.com/hightemp/process-manager --skill aif-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes references (resource) components.

What problem does it solve?

This Skill automates the creation of commit messages, ensuring they adhere to the Conventional Commits specification, which improves commit history readability and enables automated changelog generation.

Core Features & Use Cases

Analyzes staged changes: Automatically inspects git diff --cached to understand modifications.
Determines commit type: Selects appropriate types like feat, fix, docs, etc.
Identifies scope: Infers scope from file paths or uses provided arguments.
Generates semantic messages: Crafts subject lines, bodies, and footers according to the specification.
Handles breaking changes: Correctly formats BREAKING CHANGE footers.
Offers to push: Prompts to push commits after a successful git commit.

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

This Skill analyzes staged Git changes via `git diff --cached` to automatically generate conventional commit messages. It determines the appropriate commit type, infers scope from file paths, and formats the subject, body, and footers to adhere to the specification.

Can I automatically infer the commit scope from modified file paths?▼

Yes, you can automatically infer the commit scope from modified file paths during message generation. The tool analyzes staged file changes to identify the appropriate scope, or you can explicitly provide scope arguments to override the automatic detection.

How do I format breaking changes in semantic commits?▼

To format breaking changes in semantic commits, the tool automatically appends a correctly formatted `BREAKING CHANGE` footer to your commit message. This ensures compliance with the Conventional Commits specification when analyzing staged modifications.

Do I need Git installed to generate semantic commit messages locally?▼

Yes, you need Git installed locally to generate semantic commit messages. The tool explicitly depends on Git commands to analyze staged diffs and execute the final commit creation process on your local repository.

Can I push to a remote repository immediately after creating a semantic commit?▼

Yes, you can push to a remote repository immediately after creating a semantic commit. Following a successful `git commit`, the tool offers a prompt to automatically execute a post-commit push action to update your remote branch.