commit

Stage and commit git changes with conventional commit messages.

9|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/0xrafasec/ai-workflow --skill commit-0xrafasec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/0xrafasec/ai-workflow/tree/main/skills/commit
Command: npx skills add https://github.com/0xrafasec/ai-workflow --skill commit-0xrafasec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of staging and committing changes in a git repository, ensuring that commits are focused, well-documented, and follow best practices.

Core Features & Use Cases

  • Conventional Commit Messages: Automatically generates conventional commit messages that adhere to best practices.
  • Change Grouping: Helps group changes logically into separate commits.
  • Commit Review: Allows users to review and approve the commit plan before execution.

Quick Start

Run the commit skill to stage and commit your changes, ensuring they are split into logical commits.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automatically generate conventional commit messages in git?

You can automatically generate conventional commit messages in git by using this Skill to automate the staging process, ensuring each commit focuses on a single concern and adheres to best practices.

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

The best way to group code changes into logical commits is using a tool that helps group changes by concern, generates conventional commit messages, and provides a review step before final execution.

Can I review my git commit plan before the changes are executed?

Yes, you can review your git commit plan before execution because this Skill provides a dedicated commit review step, allowing you to approve the logical grouping and conventional commit messages before finalizing.

Does this conventional commit tool require any specific version control setup?

This conventional commit tool requires git for version control, functioning without additional dependencies to automate staging, generate messages, and execute commits within your existing repository.

Why should I split my git changes into focused commits instead of one batch?

You should split your git changes into focused commits because it ensures commits are well-documented, grouped logically by concern, and follow conventional commit best practices for clearer version control history.