aif-commit

Generates Conventional Commits messages by analyzing staged git changes and active plan context.

31|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/letuhao/lore-weave --skill aif-commit-letuhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-commit
Source: https://github.com/letuhao/lore-weave/tree/main/.cursor/skills/aif-commit
Command: npx skills add https://github.com/letuhao/lore-weave --skill aif-commit-letuhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured commit messages is tedious, and teams often end up with inconsistent history that breaks changelogs and semantic versioning. This Skill analyzes your staged changes and produces commit messages that follow the Conventional Commits specification automatically. ## Core Features & Use Cases - Staged Diff Analysis: Runs git status and git diff --cached to determine the correct commit type (feat, fix, docs, refactor, etc.) and scope from file paths. - Plan-Aware Grouping: Reads the active plan's Commit Plan section to split staged work into multiple logical commits, including hunk-level staging when one file spans groups. - Context Gates: Checks architecture, rules, and roadmap artifacts read-only and reports WARN/ERROR findings before committing. - Use Case: After finishing an authentication feature, stage your changes and invoke the skill; it proposes "feat(auth): add password reset functionality", confirms with you, commits, and optionally pushes to the remote branch. ## Quick Start Stage your changes with git add, then ask the assistant to commit the staged changes using 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 a conventional commit message from staged changes?

Stage your files with git add, then invoke the skill. It runs git status and git diff --cached, determines the type (feat, fix, docs, etc.) and scope, proposes a message, and asks for your confirmation before committing.

What commit types does the Conventional Commits specification support?

The skill supports feat, fix, docs, style, refactor, perf, test, build, ci, and chore. It selects the type automatically from the staged diff content and keeps the subject under 72 characters in imperative mood.

Can I split staged changes into multiple commits automatically?

Yes. If the active plan contains a Commit Plan section, the skill maps staged files and hunks to planned groups, confirms the grouping with you, and commits each group separately, using hunk-level staging when one file spans groups.

Does the skill push to remote after committing?

By default it offers to push after a successful commit, using git push -u origin <branch> when no upstream exists. Setting git.skip_push_after_commit to true in .ai-factory/config.yaml disables the push prompt entirely.

What happens if nothing is staged when I run the commit command?

The skill checks git status first and shows a warning suggesting you stage changes before proceeding. It will not generate a commit message or commit anything when the staging area is empty.