skills.rest
snow-jallen
snow-jallenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Standardize squad development with a three-branch git workflow.

7|Updated Oct 24, 2020
Search Tags:#git#workflow#worktrees#branching#code-review#squad
One-click install
npx skills add https://github.com/snow-jallen/HomeSpeaker --skill git-workflow-snow-jallen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill git-workflow-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with inconsistent coordination and merge conflicts as they scale, lacking a standardized workflow and scalable issue-handling practices.

Core Features & Use Cases

  • Three-branch model (main, dev, insiders) with clear purposes and publish semantics.
  • Branch naming conventions to organize work and track issues efficiently.
  • Support for per-issue work via git worktrees and multi-repo coordination to isolate work and reduce conflicts.
  • Clear workflows for creating, updating, and merging work, including PR readiness and cleanup steps.

Quick Start

Create a new squad issue branch from dev and begin work using the squad workflow.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What is a dev-first git workflow for squad-scale collaboration?▼

A dev-first git workflow standardizes team software development using a three-branch model with main, dev, and insiders branches to organize feature work, bug fixes, and releases while reducing merge conflicts.

How do I manage multiple issues in git without branch conflicts?▼

You can manage multiple issues by using git worktrees to create per-issue branches from the dev branch, ensuring per-worktree isolation to handle work independently and reduce cross-repo coordination conflicts.

What's the best way to standardize git branch naming for feature work and bug fixes?▼

The best way to standardize git branch naming is adopting a squad workflow that defines clear conventions for tracking issues across feature work, bug fixes, and releases within your three-branch model.

Does this squad git workflow support cross-repo coordination?▼

Yes, the squad git workflow supports cross-repo coordination by applying branch naming conventions and per-issue worktree isolation across multiple repositories, ensuring standardized PR preparation and cleanup procedures.

How do I prepare a PR and clean up branches after feature work in a three-branch model?▼

To prepare a PR in a three-branch model, you follow the squad workflow's defined readiness steps to merge work from your issue branch into dev, then execute the cleanup procedures to remove the isolated git worktree.

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
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
belokonmbelokonm
8

git-workflow-manager

Design scalable Git branching models and pull request governance workflows.

Community
Advanced