git-workflow

Enforce a dev-first squad branching workflow with git worktrees and draft PRs.

Updated Apr 10, 2026

Search Tags:#git #workflow #github #branching #worktree #pr #dev

Ready to run

npx skills add https://github.com/chdaly/eshop --skill git-workflow-chdaly

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad uses a dev-first branching model to ensure feature work starts from a stable integration baseline and to reduce mainline risk.

Core Features & Use Cases

Branching policy: enforce three-branch model (main, dev, insiders) and consistent branch naming like squad/{issue-number}-{slug}.
Issue-driven work: create per-issue branches, track progress with labels, and manage PRs to dev.
Parallel work with worktrees: support multiple issues simultaneously without file-system conflicts using git worktree.

Quick Start

Initialize a new squad by creating a branch from dev named squad/{issue-number}-{slug} and start work with a draft PR to dev.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I enforce a dev-first branching model with git and GitHub CLI?▼

A dev-first branching model is enforced by automating a three-branch structure (main, dev, insiders) with per-issue squad branches and draft PRs to dev. This ensures feature work starts from a stable integration baseline and reduces mainline risk.

How do I use git worktree to manage parallel work on multiple GitHub issues?▼

Git worktree manages parallel work by creating isolated working directories for multiple issues simultaneously without file-system conflicts. This allows per-issue squad branches to be developed concurrently using a shared local repository.

What is the best way to automate branch naming conventions for issue-driven development?▼

Automating branch naming conventions requires enforcing a strict format like squad/{issue-number}-{slug} for all new branches. This links branches directly to GitHub issues and tracks progress using labels throughout the workflow.

Do I need GitHub CLI to create and manage draft PRs to a dev branch?▼

GitHub CLI is required to create and manage draft PRs to the dev branch programmatically. The workflow depends on the CLI to automate issue-driven PR creation and enforce the dev-first squad branching policy.

How does a three-branch model with main, dev, and insiders branches reduce mainline risk?▼

A three-branch model reduces mainline risk by isolating feature work in a stable dev integration baseline before reaching main. The insiders branch provides early access while ensuring only stable code progresses to main.

Can I use my existing git workflow with a dev-first squad branching model?▼

Existing git workflows must adapt to the dev-first squad model by adopting the three-branch structure and specific branch naming conventions. Teams must transition to creating per-issue branches from dev and submitting draft PRs to dev.