commit

Group staged changes into logical Git commits with conventional messages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating clear, logical, and descriptive Git commits, ensuring that your version control history accurately reflects the evolution of your codebase.

Core Features & Use Cases

  • Logical Commit Grouping: Automatically identifies and groups related changes into distinct commits.
  • Descriptive Message Generation: Crafts detailed commit messages that explain the 'what' and 'why' of each change.
  • User Confirmation: Requires explicit user approval before executing any commits, preventing accidental or unwanted changes.
  • Use Case: After a coding session, use this Skill to review all your modifications, have it suggest logical commits like "feat(auth): implement OAuth login" and "fix(ui): correct button alignment", and then confirm each one before they are added to your Git history.

Quick Start

Use the commit skill to review my changes and prepare the first logical commit.

Frequently Asked Questions about commit

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

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

To generate descriptive Git commit messages, this Skill analyzes your staged code modifications, groups related changes into logical commits, and crafts detailed explanations adhering to conventional commit standards before prompting for your confirmation.

What is the best way to group related code modifications into logical commits?

The best way to group code modifications into logical commits is using this Skill to automatically analyze your codebase changes, identify related updates, and separate them into distinct commits with descriptive messages explaining the what and why of each modification.

How does conventional commit standard formatting work for Git commit messages?

Conventional commit standard formatting works by structuring Git commit messages with specific types, scopes, and detailed explanations, which this Skill applies automatically when generating your commit messages to ensure your version control history accurately reflects codebase evolution.

Can I review and confirm Git commits before they are executed?

Yes, you can review and confirm Git commits before execution because this Skill requires explicit user approval for every suggested commit, preventing accidental or unwanted changes from being added to your version control history.

Do I need any dependencies to automate my development workflow commits?

No dependencies are required to automate your development workflow commits, as this Skill operates independently to analyze staged changes, group them logically, and generate conventional commit messages without needing external tools or libraries.

Why should I use an automated tool for version control commit messages?

You should use an automated tool for version control commit messages to streamline the process of creating clear and descriptive Git commits, ensuring your history accurately reflects codebase evolution without manual message writing effort.