create-commit

Generate conventional commit messages for staged Git changes.

Updated Apr 14, 2025

Search Tags:#git #version control #conventional commits #commit messages #commit automation

Ready to run

npx skills add https://github.com/vladpolewoi/config76 --skill create-commit-vladpolewoi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-commit
Source: https://github.com/vladpolewoi/config76/tree/main/claude/skills/create-commit
Command: npx skills add https://github.com/vladpolewoi/config76 --skill create-commit-vladpolewoi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of conventional commit messages for staged changes, following the Conventional Commits spec and VGV workflow, thus simplifying the commit process and maintaining a clean commit history.

Core Features & Use Cases

Conventional Commit Message Generation: Automatically proposes conventional commit messages that adhere to the Conventional Commits spec.
Commit Control: Offers control over whether to create a single or multiple commits, allowing for better code organization.
Use Case: Ideal for developers looking to ensure that their commit messages are consistent and follow best practices.

Quick Start

To create a commit, simply activate the skill and provide any optional arguments such as 'single-commit' or a ticket number (e.g., 'VGV-123').

Frequently Asked Questions about create-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?▼

You can generate conventional commit messages by activating the skill, which parses your arguments and gathers context from the Git repository to propose messages following the Conventional Commits spec. You can then create single or multiple commits based on your input.

What are conventional commits and why should I use them for version control?▼

Conventional commits are a standardized format for structuring commit history that this skill automates for your version control workflow. By enforcing the Conventional Commits spec, it ensures consistent documentation of project changes across single or multiple commits.

Can I create multiple commits from staged changes instead of a single commit?▼

Yes, you can control whether to create a single or multiple commits from your staged changes by providing optional arguments like 'single-commit'. This allows for better code organization based on your staged changes and proposed messages.

How do I include a ticket number like VGV-123 in my commit messages?▼

You include a ticket number by providing it as an optional argument, such as 'VGV-123', when activating the skill. The automation parses these arguments and integrates the ticket reference into your generated conventional commit message.

Does this commit automation tool work without any external dependencies?▼

Yes, this commit automation works without external dependencies, using only its internal scripts and references to parse arguments and gather context. It independently proposes conventional commit messages based on your Git repository data.