git-workflow-and-versioning

Name: git-workflow-and-versioning
Availability: InStock
Author: kevindree

Structures git branching, committing, conflict resolution, and workflow for reviewable code changes.

Updated May 3, 2026

Search Tags:#git #code review #versioning #worktrees #branching #commits #trunk-based development

Ready to run

npx skills add https://github.com/kevindree/geehoo-gateway --skill git-workflow-and-versioning-kevindree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow-and-versioning
Source: https://github.com/kevindree/geehoo-gateway/tree/main/.github/skills/git-workflow-and-versioning
Command: npx skills add https://github.com/kevindree/geehoo-gateway --skill git-workflow-and-versioning-kevindree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage code changes with disciplined git practices so small mistakes do not turn into hard-to-review, hard-to-revert messes.

Core Features & Use Cases

Atomic, descriptive commits that separate features, refactors, and fixes.
Short-lived feature branches and trunk-based habits for safer collaboration.
Worktree-based parallel work for multiple AI agents or tasks at once.
Change summaries, pre-commit hygiene, and git debugging techniques for clearer reviews and faster recovery.

Quick Start

Use this skill to review your current changes, choose the right branch strategy, create one logical commit, and write a clear summary of what changed.

Frequently Asked Questions about git-workflow-and-versioning

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

FAQPage Schema

How do I keep git changes clean and reversible during code review?▼

Use atomic, descriptive commits that separate features, refactors, and fixes to keep git changes clean and reversible. This ensures small, reviewable code changes that are easy to revert during code review.

What is the best way to manage multiple parallel AI tasks with git worktrees?▼

Git worktrees allow worktree-based parallel work for multiple AI agents or tasks at once. This approach lets you manage multiple isolated branches simultaneously without stashing or committing incomplete changes in your main directory.

How do I structure atomic commits for safer trunk-based development?▼

Structure atomic commits by isolating single logical changes, such as one feature or one fix, and writing descriptive messages. Trunk-based development relies on these short-lived feature branches to keep the main branch deployable and safe.

Can I use this git workflow for release stabilization and conflict resolution?▼

Yes, this git workflow applies to release stabilization and conflict resolution. It enforces pre-commit checks and reversible history management, ensuring that your main branch remains deployable while you resolve conflicts and stabilize releases.

How do I debug code issues through git history inspection?▼

Debug code issues through git history inspection by analyzing descriptive commit messages and isolated atomic changes. This disciplined history management makes it easier to trace specific bugs and revert problematic commits without affecting unrelated features.