skills.rest
lbouriez
lbouriezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Automate standardized Git workflows with a dev-first branching model.

Updated Mar 27, 2026
Search Tags:#git#workflow#branching#worktree#pr#dev#squad
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill git-workflow-lbouriez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/git-workflow
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill git-workflow-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad projects often struggle with inconsistent branching and PR practices. This Skill codifies a dev-first three-branch model and structured workflows to reduce context switching and merge conflicts.

Core Features & Use Cases

  • Three-branch model: main, dev, insiders with clear publish rules.
  • Branch naming conventions: squad/{issue-number}-{slug} to align work across issues.
  • End-to-end workflow: from issue initiation to PR merge targeting dev, including draft PRs.
  • Worktrees for multi-issue work: isolated working directories to parallelize work without conflicts.

Quick Start

Create a feature branch from dev, implement changes, push to origin, 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 and PR workflows across multiple issues?▼

Standardize Git workflows by enforcing a dev-first three-branch model with main, dev, and insiders channels. This codifies branch naming conventions and structured PR processes to ensure consistent collaboration and safe handoffs across multi-issue development.

What is a dev-first Git workflow and when do I need it?▼

A dev-first Git workflow directs all feature branches and pull requests to target a dedicated dev branch before merging to main. You need this branching model for multi-issue development and cross-repo coordination to reduce context switching and merge conflicts.

Can I use Git worktrees to parallelize feature work without causing conflicts?▼

Yes, Git worktrees create isolated working directories for multi-issue work. This allows you to parallelize feature development across separate branches simultaneously without conflicts, ensuring safe handoffs within your squad.

How do I name branches and structure pull requests for squad projects?▼

Name branches using the squad/{issue-number}-{slug} convention to align work across issues. Structure pull requests by opening a draft PR targeting the dev branch, following the end-to-end workflow from issue initiation to final merge.

Does this Git workflow support cross-repo coordination and draft PRs?▼

Yes, the workflow applies to cross-repo coordination and includes the full PR lifecycle. It supports opening draft PRs targeting the dev branch to facilitate structured reviews and safe handoffs before final integration into the insiders or main channels.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
webmaxruwebmaxru
49

git-workflow

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

Community
Advanced
chdalychdaly

git-workflow

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

Community
Advanced
cosmixcosmix
53

git-workflow

Standardize Git branching, commits, and pull request workflows.

Community
Intermediate