git-workflow

Manage a three-branch Git workflow with standardized issue branching and PR creation.

3.1k|475|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/bradygaster/squad --skill git-workflow-bradygaster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/bradygaster/squad/tree/main/.squad/skills/git-workflow
Command: npx skills add https://github.com/bradygaster/squad --skill git-workflow-bradygaster

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a robust and opinionated Git branching model and workflow to manage feature development, integration, and releases efficiently, especially for teams using a dev-first approach.

Core Features & Use Cases

  • Three-Branch Model: Enforces a clear separation between main (production), dev (integration), and insiders (preview).
  • Standardized Branching: Implements a consistent naming convention for issue branches (squad/{issue-number}-{slug}).
  • Efficient Multi-Issue Handling: Leverages git worktree for parallel development on multiple issues within the same repository without conflicts.
  • Multi-Repo Coordination: Guides on managing cross-repository dependencies and coordinated PRs.

Quick Start

Use the git-workflow skill to create a new branch for issue 123 with the slug 'add-user-auth'.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I manage a git workflow with multiple branches for integration and production?

A git workflow with main, dev, and insiders branches separates production, integration, and preview environments. This three-branch model enforces clear separation between releases, ongoing development, and early previews to prevent common merging errors.

How do I use git worktree for parallel development on multiple issues?

Git worktree enables parallel development by creating separate working directories for multiple issues within the same repository. This prevents branch switching conflicts and allows simultaneous work on different features without disrupting your current local environment.

What's the best way to standardize git branching for issue tracking and pull requests?

Standardize git branching by using a consistent naming convention like squad/{issue-number}-{slug} for issue branches. This creates predictable branch names and ensures pull requests consistently target the dev integration branch instead of main.

Can I coordinate pull requests across multiple repositories with a dev-first branching strategy?

Multi-repository coordination is supported for managing cross-repository dependencies and synchronized pull requests. This guides teams through creating coordinated PRs across repos while maintaining a dev-first integration approach.

Does this branching model work for teams already using a dev branch for integration?

This model is specifically designed for teams using a dev-first approach for feature integration. It enforces best practices by routing all issue branches and pull requests to the dev branch, keeping the main branch reserved strictly for production releases.

Why should pull requests target the dev branch instead of main in this workflow?

Pull requests target the dev branch to maintain a stable main branch reserved for production. This prevents unreviewed or unstable code from reaching production and establishes a clear integration testing phase before any final release.