skills.rest
sytone
sytoneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Enforce a three-branch Git model with per-issue worktrees.

2|3|Updated Apr 1, 2026
Search Tags:#git#workflow#collaboration#worktrees#branching#version-control#dev-ops
One-click install
npx skills add https://github.com/sytone/botnexus --skill git-workflow-sytone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/sytone/botnexus --skill git-workflow-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad relies on a coordinated git workflow to prevent diverging branches and PR conflicts across multiple developers.

Core Features & Use Cases

  • Three-branch model: main, dev, insiders to manage releases and previews.
  • Per-issue worktrees: isolated environments per issue to avoid conflicts.
  • Per-Worktree Agent Workflow: consistent, repeatable task flow per issue to coordinate work across repos.

Quick Start

Create a new feature branch from dev (squad/{issue-number}-{slug}) 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 multi-branch git workflows without causing PR conflicts across developers?▼

Git workflow coordination uses a three-branch model with main, dev, and insiders branches to manage releases and previews. This structure prevents diverging branches and PR conflicts across multiple developers collaborating in the same repository.

What is the best way to isolate feature development branches in version control?▼

Isolating feature development branches is best achieved using per-issue worktrees. This approach creates isolated environments for each issue, preventing local file conflicts and ensuring a consistent, repeatable task flow for cross-repo coordination.

How do I create a feature branch from a dev branch in a collaborative git workflow?▼

To create a feature branch from dev in a collaborative git workflow, name the branch squad/{issue-number}-{slug} and open a draft PR targeting the dev branch. This maintains a dev-first release flow for smooth team collaboration.

Can I use per-issue worktrees for cross-repo coordination across teams?▼

Yes, per-issue worktrees support cross-repo coordination across teams by applying a per-worktree agent workflow. This enforces consistent task flows per issue, allowing multiple teams to coordinate feature work safely across repositories.

When do I need a three-branch model for version control?▼

A three-branch model for version control is needed when managing releases and previews in squad development. It separates main, dev, and insiders branches to prevent diverging branches and PR conflicts during multi-branch feature development.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
Golnaz89Golnaz89

git-workflow

Enforce a dev-first three-branch Git model with insiders preview.

Community
Advanced
webmaxruwebmaxru
49

git-workflow

Coordinate multi-repo development with a three-branch Git workflow.

Community
Advanced
LeanEntropyLeanEntropy

git-workflow

Standardizes GitFlow branching, commit messages, merge strategies, and PR guidelines for managed releases.

Community
Basic