git-workflow

Enforce a dev-first three-branch model with main, dev, and insiders.

66|41|Updated Mar 4, 2026

Search Tags:#git #workflow #branching #worktree #dev #squad #insiders

Ready to run

npx skills add https://github.com/olivomarco/vbd-copilot --skill git-workflow-olivomarco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill git-workflow-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad uses a three-branch model to prevent direct work on main and coordinate releases via dev and insiders branches, improving predictability and review cycles.

Core Features & Use Cases

Three-branch workflow: main for released code, dev for integration, insiders for early access and syncs.
Branch naming conventions: issue-based squad branches to keep work organized.
Common workflows: guidelines for single-issue work, parallel worktrees, and multi-repo coordination.
Promotion pipeline: automated progression from dev to insiders and then to main after validation.

Quick Start

Begin from the dev branch, create a squad/issue-number-slug feature branch from dev, implement changes, and open a draft PR targeting dev.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

What is a dev-first three-branch git workflow?▼

A dev-first three-branch git workflow uses main for released code, dev for integration, and insiders for early access. It prevents direct work on main, coordinating releases through staged promotion pipelines to improve predictability and review cycles.

How do I start feature development using a three-branch model?▼

To start feature development in a three-branch model, begin from the dev branch and create a squad/issue-number-slug feature branch. Implement your changes there, then open a draft PR targeting dev for integration and review.

Can I use git worktrees for parallel issue branches in this workflow?▼

Yes, the git workflow supports parallel worktrees for multi-repo coordination. It provides documented procedures and common workflow guidelines for managing parallel worktrees alongside single-issue work within the dev and insiders branch structure.

How does code progress from dev to main in this branching model?▼

Code progresses through an automated promotion pipeline from dev to insiders, and finally to main. This staged release process ensures validation occurs at each step before merging changes into the protected main branch.

Why use an insiders branch for early access in software delivery?▼

An insiders branch provides early access and syncs for upcoming releases. It separates staged features from the dev integration branch, reducing coordination risks and allowing teams to validate code before final promotion to main.