v-git

Name: v-git
Availability: InStock
Author: kks0488

Enforce atomic commits with mandatory splitting and standardized messages.

26|3|Updated Jan 10, 2026

Search Tags:#git #workflow #code-review #atomic-commits #version-control #commit-splitting

Ready to run

npx skills add https://github.com/kks0488/vibe-claude --skill v-git

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: v-git
Source: https://github.com/kks0488/vibe-claude/tree/main/skills/v-git
Command: npx skills add https://github.com/kks0488/vibe-claude --skill v-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers maintain a clean, atomic git history by enforcing granular commits and a clear narrative for project development.

Core Features & Use Cases

Atomic commits: one logical change per commit to ensure easy rollback and code review.
Mandatory splitting: ensures a minimum number of commits when multiple files are touched, promoting modular changes.
Style detection: aligns commit messages with project conventions by analyzing existing history and applying consistent formatting.
Use Case: When refactoring a module across several files, plan and execute separate commits for each concern to keep history readable.

Quick Start

Use v-git to split changes into atomic commits with a consistent commit message template.

Frequently Asked Questions about v-git

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

FAQPage Schema

How do I enforce atomic commits when working across multiple files?▼

Atomic commits isolate one logical change per commit to ensure easy rollback and code review. You enforce them by splitting multi-file changes into separate concerns, such as separating UI, logic, and config updates into distinct commits.

What is the best way to split a large codebase refactoring into readable git history?▼

Splitting a large codebase refactoring involves planning separate commits for each module concern. This modular approach maintains a readable history by ensuring multi-file changes are divided into granular, traceable updates.

How do I standardize commit messages to match my project's existing conventions?▼

Standardizing commit messages involves analyzing existing project history to detect style conventions. A standardized commit message template is then applied to ensure new commits align with the project's formatting rules.

Does this atomic commit workflow support test and implementation splits?▼

Atomic commit workflows support test-plus-implementation splits alongside UI, logic, and config separation. This ensures granular version control across both small and large codebases for clean project development.

When should I use mandatory commit splitting in version control?▼

Mandatory commit splitting should be used when touching multiple files to promote modular changes. It enforces a minimum number of commits, ensuring a clear narrative and traceable git history for project development.