commit

Generate Conventional Commits messages from staged Git changes.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Donngi/agent-skills --skill commit-donngi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Donngi/agent-skills/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/Donngi/agent-skills --skill commit-donngi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Git commits, ensuring adherence to established conventions and saving developers time by intelligently classifying and splitting changes.

Core Features & Use Cases

  • Conventional Commits: Automatically generates commit messages following the Conventional Commits standard (type, scope, subject, body).
  • Change Classification: Analyzes code changes to determine the appropriate commit type (feat, fix, refactor, etc.).
  • Automatic Splitting: Identifies and suggests splitting large or mixed changes into multiple, logically distinct commits.
  • Use Case: After making several unrelated changes to a codebase, use this Skill to generate separate, well-formatted commits for each feature addition, bug fix, and documentation update.

Quick Start

Use the commit skill to create a commit for the current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged Git changes?

To generate conventional commit messages, the Skill analyzes your staged Git changes, automatically classifies the commit type, such as feat or fix, and structures the message according to Conventional Commits standards.

Can Git commits be automatically split when I have mixed code modifications?

Yes, Git commits can be automatically split. The Skill identifies large or mixed modifications and intelligently suggests dividing them into multiple, logically distinct commits for better version control history.

What is the best way to ensure my commit body has accurate context?

The best way to ensure accurate commit bodies is to let the Skill prompt you for missing context. It analyzes changes and interactively asks for additional details to complete the commit message body.

Does this tool support standard Git types like feat, fix, and refactor?

Yes, the tool supports standard Git types. It analyzes your code changes and classifies them into appropriate Conventional Commits types, including feat, fix, and refactor, for precise version control tracking.

Why should I use Conventional Commits instead of writing plain Git commit messages?

Using Conventional Commits ensures your Git history follows established conventions, making it easier to track features and fixes. This Skill automates that formatting, saving developers time and ensuring message consistency.

What should I do if my staged changes include multiple unrelated features and bug fixes?

If staged changes include unrelated features and fixes, the Skill detects the mixed modifications and suggests splitting them into separate, well-formatted commits for each specific code change.