skills.rest
Golnaz89
Golnaz89COMMUNITY
Explore all skills by this author →
Website𝕏@Golnaz89GitHub

git-workflow

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

Updated Jan 5, 2026
Search Tags:#git#workflow#worktrees#branching#pr#dev#insiders
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill git-workflow-golnaz89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill git-workflow-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and accelerates team Git collaboration by enforcing a dev-first branching model with insiders preview channel, reducing confusion and merge conflicts.

Core Features & Use Cases

  • Three-branch workflow: main, dev, insiders to separate release, integration, and early-access channels.
  • Issue-driven work: squad/{issue-number}-{slug} branches from dev, with status labels and PR progression.
  • Worktrees and multi-repo coordination: parallel issues and downstream repos with isolated working directories.
  • Post-merge discipline: cleanup steps to keep dev aligned and branches tidy.

Quick Start

Create a new squad branch from dev for your issue and open a draft PR against dev.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I structure a Git workflow with main, dev, and insiders branches?▼

A Git workflow with main, dev, and insiders branches separates release, integration, and early-access channels. You create issue-driven squad branches from dev, progress them through PRs, and merge back into dev to keep integration aligned before release.

What is the best way to manage multiple parallel Git issues in one repository?▼

Managing parallel Git issues is done using isolated worktrees. Worktrees create separate working directories for each issue-driven squad branch, allowing you to context-switch between tasks without stashing or cloning the repository multiple times.

How do I enforce consistent branch naming for issue-driven development?▼

Consistent branch naming for issue-driven development is enforced by using a squad/{issue-number}-{slug} format. Branches are created directly from the dev branch and labeled with status indicators to track their PR progression.

Do I need draft PRs for a three-branch Git workflow?▼

Draft PRs are used in this three-branch Git workflow to signal work in progress. You open a draft PR against the dev branch from your squad branch, allowing early review while indicating the code is not ready for final integration.

How does post-merge cleanup work in a dev-first branching model?▼

Post-merge cleanup in a dev-first branching model involves deleting the squad branch and synchronizing your local dev branch. This discipline keeps branches tidy and ensures the integration channel remains aligned after a pull request is merged.

Can I coordinate Git worktrees across multiple downstream repositories?▼

Git worktrees can coordinate parallel issues across multiple downstream repositories. This multi-repo coordination uses isolated working directories to manage dependencies and structured branch naming simultaneously across linked projects.

Related Skills

Explore More Software Engineering Skills→
chdalychdaly

git-workflow

Enforce a dev-first squad branching workflow with git worktrees and draft PRs.

Community
Advanced
jperezdelrealjperezdelreal

git-workflow

Standardize squad Git workflows with a three-branch model and naming conventions.

Community
Intermediate
AlejandroFerpAlejandroFerp

branch-pr

Enforce issue linkage and single type:* labels on GitHub PRs.

Community
Intermediate
webmaxruwebmaxru
49

git-workflow

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

Community
Advanced