commit

Group staged and unstaged changes into conventional git commits.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/SelrahcD/claude-marketplace --skill commit-selrahcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SelrahcD/claude-marketplace/tree/main/selrahcd-dot-claude/skills/commit
Command: npx skills add https://github.com/SelrahcD/claude-marketplace --skill commit-selrahcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create git commits with meaningful messages. Use when the user says "commit", wants to commit changes, or has finished implementing a feature.

Core Features & Use Cases

  • Automated grouping: Analyze changes and group into logical commits.
  • Conventional messages: Draft messages following the conventional-commit standard.
  • Safe staging: Stage only relevant files and ensure commits reflect a single task or feature.

Quick Start

Invoke the commit skill to analyze your changes and create a well-formed 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 create conventional commit messages from staged and unstaged git changes?

To create conventional commit messages, the skill analyzes your staged and unstaged git changes, groups them logically, and drafts a standard format message. It stages only selected files to ensure commits reflect a single feature safely.

What is the best way to group multiple file changes into a single logical git commit?

Grouping multiple file changes into a logical git commit is handled by analyzing the changes and prompting for grouping when needed. This ensures your commit reflects a single task or feature without mixing unrelated modifications.

Can I automate git commit message generation without manually staging files first?

Yes, you can automate git commit message generation without manually staging files first. The skill handles safe staging by staging only relevant files itself, ensuring a non-destructive commit process that protects your working directory.

When do I need to use conventional commits standard for my version control workflow?

You need conventional commits for version control when you want precise, meaningful commit messages that standardize your developer workflow. It enforces a standard format to clearly communicate the purpose of each change.

Does the automated commit process modify or destructively alter my unstaged changes?

The automated commit process does not destructively alter your unstaged changes. It enforces safe commits by staging only the selected, relevant files for the specific logical group, leaving the rest of your working directory untouched.