skills.rest
sachinnair90
sachinnair90COMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Coordinate Squad-style Git branching with dev-first issue branches and draft pull requests.

Updated Apr 3, 2026
Search Tags:#git#pull request#worktrees#github#branching#release workflow
One-click install
npx skills add https://github.com/sachinnair90/gitgloss --skill git-workflow-sachinnair90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill git-workflow-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes a Squad-style Git workflow so teams avoid inconsistent branching, accidental work on main, and messy handoffs between development and release channels.

Core Features & Use Cases

  • Dev-first branching: Starts all feature work from dev and keeps main reserved for released code.
  • Issue-based branches and PRs: Uses squad/{issue-number}-{slug} branches with draft pull requests targeting dev.
  • Parallel worktree coordination: Supports multiple simultaneous issues without branch-switching collisions.
  • Promotion and cleanup guidance: Covers merging to dev, syncing insiders, releasing to main, and removing stale branches and worktrees.
  • Use case: A team handling several bug fixes at once can create isolated worktrees, track each issue independently, and merge cleanly back into the integration branch.

Quick Start

Ask the Skill to set up a dev-first Git workflow for a specific issue, create the correct branch and draft pull request, and guide the merge and cleanup steps.

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage parallel git worktrees for multiple issues without branch-switching collisions?▼

You can manage parallel git worktrees by starting feature work from dev using squad/{issue-number}-{slug} branches. This isolates simultaneous issues in separate worktrees, preventing branch-switching collisions while keeping main reserved for released code.

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

A dev-first git branching workflow starts all feature work from a dev integration branch and reserves main for released code. You need it when coordinating multiple bug fixes or features simultaneously to avoid inconsistent branching and messy release handoffs.

How do I set up a draft pull request that targets the dev branch instead of main?▼

To set up a draft pull request targeting dev, create a squad/{issue-number}-{slug} branch from dev and open the PR against that integration branch. This keeps main protected until code is promoted through the release workflow.

What's the best way to coordinate a multi-repo release workflow across dev, main, and hotfix paths?▼

Coordinate multi-repo releases by merging feature branches into dev, syncing preview channels, and promoting to main. This workflow keeps dev, main, and hotfix paths consistent through structured promotion and cleanup steps that remove stale branches and worktrees.

Can I use this git workflow if my repository does not follow issue-based branch naming conventions?▼

This workflow requires strict branch naming conventions like squad/{issue-number}-{slug} and pull request targeting rules. Repositories without issue-based naming conventions will not benefit from the structured dev-first branching and cleanup coordination it enforces.

How do I clean up stale branches and worktrees after merging a pull request to dev?▼

After merging a pull request to dev, clean up stale branches and worktrees by following the promotion and cleanup guidance built into the workflow. This removes obsolete issue branches and syncs main, dev, and hotfix paths to keep the repository consistent.

Related Skills

Explore More Software Engineering Skills→
GEOS-ESMGEOS-ESM
43

github-workflow

Explains Git/GitHub workflow for MAPL including branching, commits, and pull requests.

Official
Intermediate
GGPromptsGGPrompts
147

merge

Merge feature branches into main and clean up worktrees using Git.

Community
Advanced
pacphipacphi
7

github-project-management

Coordinate GitHub project issues, boards, and sprints via AI swarm orchestration.

Community
Advanced
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

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

Community
Advanced