Enforce a dev-first two-branch Git workflow with branch naming and PR rules.
npx skills add https://github.com/mpaulosky/dotfiles --skill git-workflow-mpaulosky
Please help me install this Agent Skill. Skill: git-workflow Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/git-workflow Command: npx skills add https://github.com/mpaulosky/dotfiles --skill git-workflow-mpaulosky
Squad-based teams often struggle with coordination and inconsistent branching strategies, which leads to integration pain and release risk. This Skill defines a deterministic, squad-oriented Git workflow that uses a dev-first two-branch model to align development effort with stable delivery.
Start from dev, create a new squad/{issue-number}-{slug} branch, implement changes, and open a draft PR targeting dev.
High-intent search queries and answers about installing and using this skill.
A dev-first two-branch git workflow routes all feature work through a dev branch before promoting to main, improving release stability. It establishes deterministic branching rules, PR workflows, and transition steps specifically for squad-based teams to avoid integration pain and uncoordinated releases.
To set up a dev-first pull request workflow, create a squad/{issue-number}-{slug} branch from dev, implement changes, and open a draft PR targeting dev. After code review and merging into dev, the consolidated changes are later promoted to main for stable release deployment.
Coordinating parallel feature work across multiple issues uses per-issue branches following the squad/{issue-number}-{slug} format combined with dedicated worktrees. This approach isolates development environments, prevents branch collisions, and enables multiple squad members to integrate features into dev independently.
Use a two-branch dev-first git workflow when squad-based teams face integration pain and release risk from inconsistent branching strategies. It is suited for multi-issue, multi-squad environments that need deterministic release planning and safer integration before promoting code to main.
Draft PRs are a core part of this squad-oriented git workflow and should be opened targeting the dev branch immediately after branch creation. They enable early code review feedback and signal work in progress before final integration into dev and subsequent release promotion to main.
jperezdelrealStandardize squad Git workflows with a three-branch model and naming conventions.
Soul-Brews-StudioSwitch to main, pull latest changes, and delete merged branches.
AlejandroFerpEnforce issue linkage and single type:* labels on GitHub PRs.
cr330326Enforce a gitflow-like branching model with conventional commit standards.
