skills.rest
PlagueHO
PlagueHOCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Define and enforce a three-branch Git workflow with naming conventions and PR guidance.

2|1|Updated Mar 25, 2026
Search Tags:#git#workflow#worktrees#branching#pull-request#dev-branch#feature-work
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill git-workflow-plagueho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill git-workflow-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle with inconsistent release cadences and conflicting feature work across branches. This Skill defines a standard three-branch model (main, dev, insiders) and governance for issue-based work, improving predictability, release discipline, and collaboration at scale.

Core Features & Use Cases

  • Three-branch model: main (released), dev (integration), insiders (early access).
  • Issue-driven work: branch from dev using squad/{issue-number}-{slug}, draft PRs to dev.
  • Parallel worktrees: support multiple issues concurrently without conflicts.
  • PR-driven release cycle and post-merge cleanup guidelines to keep branches clean.

Quick Start

Branch from dev to start work on an issue, create the branch 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 parallel Git feature work without branch conflicts?▼

You can manage parallel Git feature work by using Git worktrees to support multiple issues concurrently without conflicts. This allows developers to isolate branch-based feature development and open draft pull requests simultaneously.

What is a three-branch Git workflow model for release management?▼

A three-branch Git workflow separates code stability into main for releases, dev for integration, and insiders for early access. This model streamlines feature development and enforces release discipline through tagged merges.

How do I structure Git branches for issue-driven development?▼

Structure Git branches for issue-driven development by branching from dev using the convention squad/{issue-number}-{slug}. Open draft pull requests targeting dev to integrate changes, then promote releases through tagged merges.

Does this Git workflow require a specific branching strategy for multiple squads?▼

This Git workflow is designed for teams coordinating multiple issues across squads. It requires adopting a dev-first branching model where feature work originates from dev and uses parallel worktrees to prevent conflicts.

What's the best way to standardize pull request cycles for team collaboration?▼

Standardize pull request cycles by enforcing a dev-first workflow with draft PRs targeting the dev branch. Post-merge cleanup guidelines keep branches clean, while tagged merges handle release promotion predictably.

When should I not use a dev-first Git workflow with worktrees?▼

A dev-first Git workflow with worktrees may not suit solo developers or projects lacking consistent release cadences. It is built for teams coordinating multiple issues who need strict release discipline and parallel feature integration.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

rebase-latest-main

Rebase a local git branch onto the latest remote main.

Community
Intermediate
lvlup-swlvlup-sw
33

cleanup

Verify merged PRs, backfill metadata, and prune git worktrees and branches.

Official
Advanced
sachinnair90sachinnair90

git-workflow

Coordinate Squad-style Git branching with dev-first issue branches and draft pull requests.

Community
Advanced
kirvinkirvin

branching-strategy

Define and implement Git branching strategies for collaborative development.

Community
Intermediate