git-workflow

Name: git-workflow
Availability: InStock
Author: sudhakrms

Enforce a dev-first branching model with an insiders preview channel.

1|Updated Apr 17, 2026

Search Tags:#git #workflow #worktrees #branching #release-management #pull-requests #dev-first

Ready to run

npx skills add https://github.com/sudhakrms/CalendarControl --skill git-workflow-sudhakrms

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and enforces a Git workflow across squads by implementing a dev-first branching model and an insiders preview channel, accelerating feature delivery while reducing integration pain.

Core Features & Use Cases

Establishes a three-branch model (main, dev, insiders) with defined publication flows.
Enforces branch naming conventions (e.g., squad/{issue-number}-{slug}) and a structured PR lifecycle.
Supports multi-issue coordination and workspaces via git worktrees and cross-repo workflows.

Quick Start

Begin by adopting the dev-first branching model and create your first squad branch from dev to start work on an issue.

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 branching model with an insiders preview channel?▼

A dev-first branching model routes feature development through a dev branch before main, while an insiders preview channel publishes early builds. This workflow accelerates feature delivery and reduces integration pain by standardizing branch flows across squads.

How do I structure Git branch naming conventions for multi-issue work?▼

Structure Git branch naming conventions using a squad-based format like squad/{issue-number}-{slug}. This enforces a structured pull request lifecycle and coordinates multi-issue workspaces when paired with git worktrees.

How do I use git worktrees for cross-repo collaboration?▼

Use git worktrees to manage multi-issue coordination by creating isolated working directories for different branches. This supports cross-repo workflows and allows simultaneous development without constantly switching branches in a single directory.

Does this Git workflow support release coordination across multiple squads?▼

Yes, this Git workflow supports release coordination by establishing a three-branch model with main, dev, and insiders branches. It defines specific publication flows to standardize releases and manage cross-repo collaboration among different squads.

When should I not use a dev-first branching model?▼

You should avoid a dev-first branching model if your project does not require strict release coordination or multi-squad governance. It enforces structured PR workflows and branch naming conventions that may introduce unnecessary overhead for small, simple repositories.

What is the best way to automate Git workflow governance for pull requests?▼

Automate Git workflow governance by enforcing a structured PR lifecycle alongside a dev-first branching model. This requires adherence to branch naming conventions and defined publication flows between main, dev, and insiders branches to standardize integration.