skills.rest
rett-europe
rett-europeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-workflow

Define a three-branch Git workflow with dev-first branching and draft PRs.

2|Updated Apr 14, 2026
Search Tags:#git#workflow#branching#pr#code-review#dev#squad
One-click install
npx skills add https://github.com/rett-europe/opentreasury --skill git-workflow-rett-europe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/rett-europe/opentreasury/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/rett-europe/opentreasury --skill git-workflow-rett-europe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad-wide branching chaos, inconsistent releases, and slow feedback loops are minimized by a standardized three-branch model and strict naming conventions.

Core Features & Use Cases

  • Three-branch model: main for released code, dev for integration, insiders for early access.
  • Issue-based branching: create branches named squad/{issue-number}-{slug} from dev to keep work organized.
  • PR workflow and release hygiene: draft PRs target dev, with clear merge strategy and post-merge cleanup to avoid drift.

Quick Start

Follow the squad workflow by branching from dev, naming your branch squad/{issue-number}-{slug}, and opening 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 three-branch Git workflow for squad development?▼

A three-branch Git workflow uses main for released code, dev for integration, and insiders for early access. It minimizes branching chaos and inconsistent releases by enforcing strict naming conventions and predictable release hygiene.

How do I structure issue-based branches and draft PRs in a squad Git workflow?▼

To structure issue-based branches, branch from dev and name them squad/{issue-number}-{slug}. Open draft PRs targeting dev to maintain organized work and clear merge strategies before integration.

Does this squad Git workflow require specific branch naming conventions?▼

Yes, the squad Git workflow requires deterministic branch naming conventions. You must name issue-driven development branches squad/{issue-number}-{slug} to keep work organized and ensure predictable releases.

What is the best way to manage branch cleanup and prevent drift in a squad Git workflow?▼

The best way to prevent drift is applying post-merge cleanup rituals. This involves deleting merged issue branches and enforcing a clear merge strategy where draft PRs target dev before final integration.

When should I use an insiders branch instead of a dev branch in a Git workflow?▼

Use an insiders branch for early access code, while reserving the dev branch for integration. This separation ensures predictable releases by isolating untested features from ongoing squad integration work.

Why does strict dev-first branching improve release predictability for squads?▼

Strict dev-first branching improves predictability by centralizing integration. All issue branches and draft PRs target dev, ensuring main only receives tested code and minimizing slow feedback loops.

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
the-agency-aithe-agency-ai
39

pr-captain-post-merge

Automates GitHub post-merge validation, release tagging, and branch cleanup workflows.

Official
Intermediate
Leep-GHLeep-GH

git-workflow

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

Community
Advanced
kirvinkirvin

branching-strategy

Define and implement Git branching strategies for collaborative development.

Community
Intermediate