git-workflow

Standardize Git branching, worktree management, and branch lifecycle closure.

5|1|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/hollandkevint/thinkhaven --skill git-workflow-hollandkevint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/hollandkevint/thinkhaven/tree/main/skills/git-workflow
Command: npx skills add https://github.com/hollandkevint/thinkhaven --skill git-workflow-hollandkevint

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures consistent and efficient Git practices across all agent workflows, preventing common issues like unmerged branches and messy histories.

Core Features & Use Cases

  • Branching Strategies: Supports both standard branching and recommended isolated worktrees for parallel development.
  • Lifecycle Management: Enforces mandatory branch closure through merging or abandonment, with an escape hatch for work-in-progress.
  • Use Case: When starting a new feature, use the worktree-feature.sh script to create an isolated environment, keeping your main branch clean. Once the feature is complete, follow the mandatory branch closure steps to merge and clean up.

Quick Start

Use the git-workflow skill to create a new feature branch named 'new-login-flow'.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I manage Git branching and worktree isolation for parallel development?

Git branching and worktree isolation for parallel development are managed by standardizing branch creation through shell scripts, ensuring your main branch remains clean while features are developed in isolated worktrees.

How do I enforce mandatory branch closure and prevent unmerged Git branches?

Mandatory branch closure and prevention of unmerged Git branches are enforced through lifecycle management rules that require branches to be explicitly merged or abandoned, with an escape hatch for work-in-progress.

What is the best way to standardize Git workflows for agent-driven tasks?

Standardizing Git workflows for agent-driven tasks involves enforcing consistent branching strategies, utilizing isolated worktrees, and mandating lifecycle closure to prevent messy commit histories across automated processes.

Do I need specific shell scripts to create and clean up Git worktrees?

Yes, specific shell scripts are required to create and clean up Git worktrees, as this Skill provides scripts for worktree creation, review, and cleanup to ensure clean Git histories.

Why does my Git branch lifecycle management leave messy histories and unmerged branches?

Git branch lifecycle management leaves messy histories when closure steps are skipped, which this Skill resolves by enforcing mandatory merging or abandonment after feature completion in isolated worktrees.