skills.rest
jperezdelreal
jperezdelrealCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

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

Updated Apr 6, 2026
Search Tags:#git#workflow#branching#code-review#version-control#squad#pr-management
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill git-workflow-jperezdelreal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill git-workflow-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad-level project collaboration often suffers from inconsistent branch strategies and noisy PR cycles. This guide defines a standard three-branch model and a naming convention to align team workflows.

Core Features & Use Cases

  • Three-branch model: main for releases, dev for integration, insiders for early access.
  • Descriptive branch naming: squad/{issue-number}-{slug} for traceability.
  • Draft PRs and reviews: PRs target dev to ensure validated changes reach the integration branch.

Quick Start

Checkout dev, create a new squad/{issue-number}-{slug} branch from dev, 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 standardize Git branching workflows for a development squad?▼

Standardize squad Git workflows by adopting a three-branch model using main for releases, dev for integration, and insiders for early access to reduce integration friction.

What is the best way to name Git branches for squad-level collaboration?▼

Name Git branches using the squad/{issue-number}-{slug} convention to ensure traceability and align team workflows when branching from the dev integration branch.

How does the draft PR process work in a three-branch model?▼

In a three-branch model, draft PRs target the dev branch to ensure validated changes reach the integration branch before moving to main for releases.

When do I need an insiders branch separate from main and dev?▼

You need an insiders branch separate from main and dev to provide early access to features while keeping the dev integration branch stable for squad collaboration.

Can I use this squad Git workflow for solo development?▼

This workflow targets squad-level project collaboration to reduce noisy PR cycles and inconsistent branch strategies, making it excessive for solo development.

Why should my team use a PR-driven release process targeting dev instead of main?▼

A PR-driven release process targeting dev ensures validated changes reach the integration branch first, preventing unreviewed code from directly entering the main release branch.

Related Skills

Explore More Software Engineering Skills→
helderbertohelderberto
114

amend-push

Amend the previous commit and push changes to a remote repository.

Community
Basic
gaiastudio-aigaiastudio-ai
2

gaia-release

Bump the GAIA version, commit, tag, push, and publish a GitHub Release.

Official
Advanced
chdalychdaly

git-workflow

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

Community
Advanced
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

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

Community
Advanced