skills.rest
barichter
barichterCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Implement a structured Git workflow with automated branch management and multi-repository integration.

Updated Apr 12, 2026
Search Tags:#git#workflow#branch management#early-access#dev-first
One-click install
npx skills add https://github.com/barichter/squad --skill git-workflow-barichter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/barichter/squad/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/barichter/squad --skill git-workflow-barichter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires squad-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing complex Git workflows, particularly for teams that need to balance feature development with stable releases and early access to new features.

Core Features & Use Cases

  • Dev-First Workflow: Ensures that all feature development occurs on a 'dev' branch, maintaining a stable 'main' branch for production.
  • Early-Access Channels: Provides an 'insiders' branch for early testing and feature previews.
  • Branch Naming Conventions: Standardizes branch naming to prevent confusion and streamline the merge process.
  • Worktrees for Parallel Development: Allows simultaneous work on multiple issues without branch conflicts.
  • Multi-Repo Coordination: Facilitates collaboration across multiple repositories with a clear merge order and testing procedures.

Quick Start

Set up your Squad team and start your first issue branch by running: git checkout dev && git pull origin dev && git checkout -b squad/123-improve-api -b squad/123-improve-api origin/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 parallel Git workflows across multiple repositories?▼

Parallel Git workflows across multiple repositories are managed using standardized branch naming, worktrees for simultaneous issue resolution, and a coordinated merge order to prevent integration conflicts.

What is the best way to set up an early-access branch for feature previews?▼

Setting up an early-access branch involves maintaining an 'insiders' branch specifically for early testing, keeping it separate from the stable 'main' production branch and the active 'dev' development branch.

How do I start a new feature branch from a dev-first Git workflow?▼

Start a new feature branch by checking out and pulling the 'dev' branch, then creating a standardized issue branch like 'squad/123-improve-api' directly from 'origin/dev' to ensure isolated development.

Can I use Git worktrees to work on multiple issues without branch conflicts?▼

Yes, Git worktrees are supported to allow simultaneous work on multiple issues without branch conflicts, enabling developers to maintain separate working directories for each feature branch.

Do I need Squad CLI to coordinate multi-repo Git branch management?▼

Yes, Squad CLI is a required dependency for executing this structured branch management workflow, as it facilitates multi-repository integration and automates the parallel development setup.

Related Skills

Explore More Software Engineering Skills→
shirulotshirulot

yeet

Automate Git staging, committing, and GitHub pull request creation.

Community
Advanced
mixomatmixomat

clean-gone-branches

Delete local git branches marked [gone] while skipping worktree branches.

Community
Intermediate
ToXMonToXMon

devops-assistant

Automate DevOps guidance for commits, deployments, and CI/CD configurations.

Community
Advanced
cpfcoachingcpfcoaching

Using Git Worktrees

Add or modify Git branches in isolated worktree directories.

Community
Advanced