git-vibe

Coordinate parallel Git work using isolated worktrees to keep main clean.

2|Updated Mar 16, 2026

Search Tags:#automation #git #workflow #branching #release #worktree

Ready to run

npx skills add https://github.com/sailscastshq/git-vibe --skill git-vibe

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git Vibe provides a safe, scalable workflow for concurrent development by using isolated worktrees and a structured main-branch model, helping teams keep main deployable while experiments run in lanes.

Core Features & Use Cases

Worktree-based lanes: each feature runs in its own worktree under feat/*, enabling parallel experiments without polluting main.
Solo mode option: switch to a single-checkout workflow when one lane suffices.
Release-driven workflow: cut releases directly from main with annotated tags, with semantic commits and lifecycle hooks.

Quick Start

Open a vibe for a feature and start working in its dedicated worktree using git vibe code <name>.

Frequently Asked Questions about git-vibe

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

FAQPage Schema

How do I use git worktrees to manage parallel feature branches without polluting main?▼

Git worktrees isolate parallel feature lanes under feat/*, keeping main deployable while experiments run. Each feature operates in its own dedicated worktree directory, preventing branch pollution during concurrent development.

What is the best way to coordinate multiple AI-assisted coding experiments in isolated git environments?▼

Coordinating AI-assisted experiments requires isolated worktrees for each lane. A worktree-first mode provides separate directories for concurrent experiments, ensuring isolated states that protect the main branch from incomplete changes.

How do I cut a release directly from main with annotated tags and semantic commits?▼

Cutting releases directly from main uses annotated tags applied to the clean main branch. The workflow enforces semantic commits throughout the feature lanes, ensuring a structured and deployable release history.

Can I switch to a single-checkout solo mode when running only one feature lane in git?▼

Solo mode provides a single-checkout workflow for when one lane suffices. You can switch from the default worktree-first mode to streamline development without managing multiple isolated worktree directories.

Does this git workflow support lifecycle hooks for branching and release automation?▼

Lifecycle hooks are supported throughout the branching and release workflow. These hooks integrate with the worktree-based lanes and semantic commits, enabling automated custom actions during feature development and release cuts.

When should I avoid using git worktrees for parallel development?▼

Avoid git worktrees when running a single feature lane where solo mode is more efficient. Worktrees add directory management overhead that is unnecessary for simple, linear development without concurrent experiments.