Git

Guide Git version control workflows with conventional commit formatting.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vdemeester/home --skill git-vdemeester
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git
Source: https://github.com/vdemeester/home/tree/main/dots/.config/claude/skills/Git
Command: npx skills add https://github.com/vdemeester/home --skill git-vdemeester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides Git usage with best practices for commits, branching, and advanced workflows, enabling clean history and robust collaboration.

Core Features & Use Cases

  • Commit Hygiene: Conventional commits with a clear rationale.
  • Branch & Merge Workflows: Branch naming, merging strategies, and conflict handling.

Quick Start

Create an atomic feature branch, commit with a descriptive message, and push.

Frequently Asked Questions about Git

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

FAQPage Schema
How do I write commit messages that follow Git best practices?▼

Conventional commits use a structured format with type, scope, and description to create clear, searchable history. This Skill guides formatting with a clear rationale, enforcing atomic commits and no emojis for professional collaboration.

What's the best way to organize branches and merge workflows?▼

Branch naming conventions and deliberate merge strategies prevent conflicts and maintain clean history. This Skill covers branch creation, merging approaches, and conflict handling to support robust team workflows.

How do I structure atomic commits in my workflow?▼

Atomic commits isolate single logical changes, making history readable and debugging easier. This Skill applies conventional commit formatting and pre-commit checks to ensure each commit serves one purpose.

Can I use rebasing, cherry-picking, and stashing together in one workflow?▼

Advanced Git operations like rebasing, cherry-picking, stashing, and worktrees compose into powerful workflows for complex scenarios. This Skill routes across all these domains with best practices for each.

How do I attribute contributions from multiple authors in Git?▼

Co-Authored-By trailers and --signoff flags document shared authorship in commit metadata. This Skill enforces these conventions alongside conventional commit formatting for transparent collaboration.

Why should I use worktrees instead of switching branches frequently?▼

Worktrees let you maintain multiple working directories on different branches simultaneously, avoiding repeated checkouts and stash churn. This Skill covers worktree workflows as an advanced alternative to traditional branch switching.