git-workflow

Standardize squad Git workflows with dev, main, and insiders branches.

9|1|Updated Jul 21, 2025
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill git-workflow-usepowershell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill git-workflow-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad teams often struggle with inconsistent branching and coordination across features, releases, and parallel work. This Skill provides a clear, repeatable Git workflow that anchors development around a dev branch, a stable main, and an insiders preview channel.

Core Features & Use Cases

  • Consistent Branching Model: Standardizes branch types (dev, main, insiders) and naming conventions to reduce confusion.
  • Parallel Work with Worktrees: Supports multiple issues in flight without branch churn by leveraging Git worktrees.
  • Structured Release Cadence: Guides when to publish and merge, from feature development to insider releases.

Quick Start

Start from the dev branch, create a squad/{issue-number}-{slug} feature branch, push your 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
How do I manage multiple concurrent workstreams in Git without branch churn?

Git worktrees manage multiple concurrent workstreams by linking separate directories to a single repository, allowing you to work on multiple issues in parallel without switching branches. This prevents branch churn and keeps development isolated.

What is the best Git branching model for squad-based feature development?

A squad-focused Git branching model anchors development around a dev branch, a stable main, and an insiders preview channel. It standardizes branch naming conventions to reduce confusion during feature development and cross-repo coordination.

How do I create a feature branch for a specific issue in a standardized workflow?

To create a feature branch, start from the dev branch and create a squad/{issue-number}-{slug} branch. Push your changes and open a draft PR targeting dev to begin the structured release cadence.

Can I use Git worktrees for parallel feature development across multiple issues?

Yes, Git worktrees support parallel feature development across multiple issues without branch churn. They allow you to maintain separate working directories for each issue concurrently within the same repository.

When do I need an insiders branch in my Git workflow?

An insiders branch is needed when guiding structured release cadences from feature development to insider releases. It serves as a preview channel alongside the dev and main branches for squad teams.

Does this Git workflow require specific tools beyond standard Git?

No specific tools beyond standard Git are required. The workflow leverages native Git worktrees and branch naming conventions to coordinate parallel work and enforce step-by-step setup and promotion guidelines.