commit

Creates git commits using conventional commit format with staged file selection.

Updated May 28, 2026
One-click install
npx skills add https://github.com/kma-core/windmill --skill commit-kma-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kma-core/windmill/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/kma-core/windmill --skill commit-kma-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-formatted git commit messages is a common friction point for developers, and inconsistent commit history makes changelogs and code archaeology harder. This Skill standardizes every commit to the conventional commit format with proper staging discipline. ## Core Features & Use Cases - Conventional Commit Formatting: Enforces the <type>: <description> single-line format with types like feat, fix, refactor, docs, style, test, chore, and perf. - Selective Staging: Stages only modified files individually, explicitly avoiding git add -A or git add . to prevent accidental commits. - Change Analysis Workflow: Runs git status, git diff, and git log to understand changes and match recent commit style before committing. - Use Case: After finishing a bug fix across three files, ask the AI to commit the changes and receive a properly formatted message like fix: resolve null pointer in job executor with only the relevant files staged. ## Quick Start Ask the AI to commit your current changes using the commit skill, and it will analyze the diff, stage the modified files, and create a conventional commit message.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a conventional commit message in git?

Use the format `<type>: <description>` as a single line, where type is one of feat, fix, refactor, docs, style, test, chore, or perf. Keep the description lowercase, imperative, under 72 characters total, with no trailing period.

How to commit only specific files in git instead of everything?

Stage files individually by name using `git add <file1> <file2>` rather than `git add -A` or `git add .`. This prevents accidentally committing unrelated or sensitive changes and keeps each commit focused.

What are the conventional commit types and when to use each?

Use feat for new features, fix for bug fixes, refactor for code changes without behavior change, docs for documentation, style for formatting, test for test changes, chore for maintenance, and perf for performance improvements.

Why should commit messages be a single line under 72 characters?

Single-line messages under 72 characters display cleanly in git log, GitHub interfaces, and terminal output without truncation. The conventional commit format also enables automated changelog generation and semantic versioning tools.

Can this skill handle multi-line commit messages or commit bodies?

No, this skill strictly enforces single-line commit messages with no body. It is designed for focused, atomic commits where the type prefix and concise description fully capture the change.