skills.rest
CarlosSardo
CarlosSardoCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Coordinate a dev-first Git workflow across main, dev, and insiders branches.

Updated Aug 23, 2026
Search Tags:#git#workflow#branching#pull-request#dev-first#insiders
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill git-workflow-carlossardo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill git-workflow-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with inconsistent Git workflows, merge strategies, and release readiness across branches, leading to delays and confusion. This skill defines a dev-first branching model that standardizes main, dev, and insiders workflows for predictable collaboration.

Core Features & Use Cases

  • Three-branch model: main (released), dev (integration), insiders (early access) with clear purposes and published flows.
  • Branch naming conventions: issue-based branches such as squad/{issue-number}-{slug} to keep work traceable.
  • Issue-driven workflow: feature work starts from dev, PRs target dev, and promotions to main/insiders follow defined gates.
  • Worktrees for parallel work: support for multiple concurrent issues using git worktree to avoid conflicts.
  • Release and promotion: automation-minded guidance for promoting changes from dev to insiders and then to main.

Quick Start

Start from the dev branch, create a feature branch from dev for your issue, and open a draft PR targeting dev when ready.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What is a dev-first Git workflow with main, dev, and insiders branches?▼

A dev-first Git workflow routes feature work through a dev integration branch before promoting changes to insiders for early access and main for releases. This three-branch model standardizes release readiness and predictable collaboration across software teams.

How do I structure issue-driven feature branches targeting the dev branch?▼

Create feature branches from dev using standardized naming conventions like squad/{issue-number}-{slug} to keep work traceable. Open a draft PR targeting dev when ready, ensuring all issue-driven work integrates predictably before promotion to insiders and main.

Can I use git worktree for parallel issue-driven development across multiple branches?▼

Yes, git worktree supports multiple concurrent issues by creating per-issue worktrees. This allows parallel work across dev, insiders, and main branches without local conflicts, fitting the three-branch model and issue-driven workflow seamlessly.

What is the best way to promote changes from dev to insiders and main branches?▼

Follow defined promotion gates to move changes from dev to insiders for early access, then to main for release. This controlled promotion enforces release readiness and standardizes the multi-branch PR workflow across the three-branch model.

Does this three-branch Git model work for teams practicing issue-driven development with pull requests?▼

Yes, it is designed for software teams practicing issue-driven work with feature branches and multi-branch PRs. The workflow enforces standardized branch naming, PR reviews, and controlled promotion from dev to insiders and main.

Why standardize branch naming conventions like squad/{issue-number}-{slug} in Git workflows?▼

Standardized branch naming keeps issue-driven work traceable across dev, insiders, and main branches. It enforces consistent PR reviews and controlled promotions, preventing delays and confusion caused by inconsistent merge strategies.

Related Skills

Explore More Software Engineering Skills→
nicolehaugennicolehaugen

git-workflow

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

Community
Intermediate
olivomarcoolivomarco
66

git-workflow

Enforce a dev-first three-branch model with main, dev, and insiders.

Community
Advanced
ToqsickToqsick

github-grayhack-workflow

Automate GitHub issue creation, branch management, pull requests, and documentation updates.

Community
Advanced
webmaxruwebmaxru
49

git-workflow

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

Community
Advanced