git-commit

Create atomic git commits with conventional commit message standards.

3|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/vekzz-dev/opencode-skills --skill git-commit-vekzz-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/vekzz-dev/opencode-skills/tree/main/git-commit
Command: npx skills add https://github.com/vekzz-dev/opencode-skills --skill git-commit-vekzz-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates messy, monolithic commits by enforcing atomic changes and standardized message formatting, ensuring your project history remains clean, readable, and bisectable.

Core Features & Use Cases

  • Atomic Change Enforcement: Guides you to split unrelated changes into separate, logical commits.
  • Conventional Commit Compliance: Automatically structures messages using the standard type(scope): description format.
  • Use Case: When you have finished a feature and a bug fix in the same session, this skill helps you stage and commit them as two distinct, verifiable units of work.

Quick Start

Ask the agent to commit your current changes using the conventional commit format and it will guide you through the atomic staging process.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create atomic git commits with conventional commit standards?

Atomic commits require splitting unrelated changes into separate logical commits. This skill enforces conventional commit standards and dependency-aware ordering, guiding you through staging distinct units of work for a bisectable history.

What is the conventional commit format for structuring git messages?

The conventional commit format structures messages using the standard type(scope): description syntax. It mandates structured commit types and requires body explanations to ensure changes are well-documented and logically grouped.

How do I split mixed feature and bugfix changes into separate commits?

To split mixed changes, you stage and commit them as distinct verifiable units of work. This atomic change enforcement separates unrelated modifications, preventing monolithic commits in your development workflow.

When do I need atomic commits in my version control workflow?

You need atomic commits when your software development workflow requires a clean, bisectable, and well-documented version control history. This is essential for maintaining code quality and logical dependency-aware commit ordering.

Does this conventional commit workflow require any specific git dependencies?

No specific dependencies are required to enforce conventional commit standards. The workflow operates directly within your software engineering environment to guide atomic staging and structured message formatting.