skills.rest
Leep-GH
Leep-GHCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Coordinate feature work, reviews, and releases across three Git branches.

Updated Apr 16, 2026
Search Tags:#git#workflow#worktrees#branching#dev#pull-request#insiders
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill git-workflow-leep-gh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill git-workflow-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns development activity with a structured, predictable Git workflow that coordinates feature work, reviews, and releases across multiple branches and issue-driven tasks.

Core Features & Use Cases

  • Three-branch model: main, dev, insiders for release, integration, and early access.
  • Branch naming: squad/{issue-number}-{slug} for issue-focused work.
  • Issue-driven PRs: draft PRs to dev and disciplined merge workflow.
  • Worktrees for parallel work: isolated environments to handle multiple issues concurrently.
  • Use cases include a single-repo feature, cross-repo coordination, and hotfix flows from main to dev.

Quick Start

Start from dev, create a squad/{issue-number}-{slug} branch, push, 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
What is a dev-first Git workflow with a three-branch model?▼

A dev-first Git workflow structures development using three branches: main for releases, dev for integration, and insiders for early access. It coordinates feature work, code reviews, and release prep across issue-driven tasks.

How do I start feature development using a squad branch naming convention?▼

To start feature development, create a branch named squad/{issue-number}-{slug} from the dev branch. Push your changes and open a draft pull request targeting dev to maintain an issue-driven merge workflow.

Can I use Git worktrees to manage multiple issue branches concurrently?▼

Yes, Git worktrees provide isolated environments to handle multiple issues concurrently. This allows parallel development across different feature branches without switching contexts in a single working directory.

What's the best way to handle hotfix flows across main and dev branches?▼

For hotfix flows, apply fixes directly to the main branch for immediate release, then merge those changes back into the dev branch to ensure integration consistency across your three-branch model.

How do pull request hygiene and issue tracking work in this Git workflow?▼

Pull request hygiene is maintained through issue-driven draft PRs targeting the dev branch. This enforces disciplined merges and links development activity directly to issue tracking using consistent branch naming.

Does this Git workflow support cross-repo coordination?▼

Yes, the workflow supports cross-repo coordination by utilizing Git worktrees for isolated environments. This enables managing dependencies and parallel work across multiple repositories simultaneously.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
AAbdulghanyAAbdulghany

release

Diff dev and main branches to determine SemVer bumps and generate CHANGELOG entries.

Community
Advanced
OirancaOiranca

ci-checks

Executes lint, type-check, test, and build commands for CI validation.

Community
Intermediate
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

Enforce small, frequent commits to the main branch for Trunk Based Development workflows.

Community
Advanced