git-workflow

Implements a three-branch Git workflow with naming conventions and worktrees for parallel issues.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill git-workflow-nicolehaugen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill git-workflow-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured workflow for managing feature development using the Squad branching model, improving collaboration and efficiency in version control.

Core Features & Use Cases

  • Squad Branching Model: Defines a clear branch structure for feature development, including main, dev, and insiders branches.
  • Branch Naming Convention: Standardizes issue branching using a consistent naming format.
  • Parallel Multi-Issue Work: Enables concurrent work on multiple issues using git worktree.
  • Multi-Repo Downstream Scenarios: Facilitates coordination across multiple repositories.

Quick Start

Apply the git-workflow skill to a project by following the guidelines for branch naming, workflow steps, and worktree setup for parallel issue management.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I manage parallel feature development across multiple Git branches?

You can manage parallel feature development using the Squad branching model, which defines a three-branch workflow with main, dev, and insiders branches, and uses git worktree for concurrent issue management.

What is the best way to coordinate version control across multiple repositories?

The Squad branching model facilitates multi-repo coordination by standardizing branch naming conventions and structuring cross-repository workflows to keep downstream development synchronized.

How do I set up git worktree for working on multiple issues at the same time?

Git worktree enables parallel multi-issue work by allowing you to maintain multiple working directories from a single repository, each mapped to a specific branch using standardized naming conventions.

Do I need a specific Git version to use the Squad branching model?

The Squad branching model requires the Git version control system, but it does not specify a minimum version requirement beyond standard support for branching and worktree functionality.

When should I use a dev branch instead of a main branch in version control?

In the Squad branching model, a dev-first workflow uses the dev branch for active feature integration, while the main branch is reserved for stable production-ready releases.

Can I use this branching model for an existing repository with an established branch structure?

You can apply this workflow to an existing repository by adopting the main, dev, and insiders branch structure alongside the standardized branch naming conventions to align with the Squad model.