skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

git-workflow

Automate squad-based Git workflows with dev/main/insiders branches.

Updated Nov 11, 2025
Search Tags:#git#workflow#branching#issue-tracking#dev#pull-request#insiders
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill git-workflow-acmeleme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill git-workflow-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad uses a three-branch model. This Skill codifies a standardized Git workflow to reduce merge conflicts and miscommunication by documenting branch strategies, naming conventions, and release processes.

Core Features & Use Cases

  • Defines dev/main/insiders branches and their purposes
  • Provides naming conventions, PR workflow, and multi-worktree setup guidance for parallel work
  • Use case: a feature work item moves from dev to insiders through PRs with clear release tagging

Quick Start

Apply the squad workflow in your repo by creating a dev branch from origin/dev, naming issue branches as squad/{issue-number}-{slug}, and opening draft PRs targeting dev.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What is the dev/main/insiders branching model for Git workflows?▼

The dev/main/insiders branching model separates feature development, stable releases, and early access previews. This Git workflow defines specific branch purposes to reduce merge conflicts and streamline squad-based software delivery through structured issue tracking.

How do I name branches and structure pull requests for issue tracking?▼

Name issue branches as squad/{issue-number}-{slug} and open draft pull requests targeting the dev branch. This Git workflow enforces standardized branch naming and PR processes to connect feature work directly to tracked issues.

Can I manage multiple worktrees for parallel Git workflow tasks?▼

Yes, this Git workflow supports multi-worktree setups. It provides structured commands and conventions for configuring parallel work environments, allowing squad members to context-switch between feature branches without stalling ongoing development.

How do features move from dev to insiders in a release workflow?▼

Features move from dev to insiders through structured pull requests with clear release tagging. This Git workflow codifies the release process to ensure feature work items progress smoothly through the multi-branch pipeline.

Does this Git workflow require a specific branching strategy to start?▼

Yes, you need to create a dev branch from origin/dev to apply the squad workflow. It requires adopting a dev-first branching model where feature work flows through dev, main, and insiders branches.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
quaid-appquaid-app
3

git-workflow

Enforce a dev-first three-branch model with issue-based workflows and PR merges.

Official
Intermediate
YoshikemoloYoshikemolo
5

git-jira-integration

Generate Git branch names and validate commit messages against Jira issues.

Community
Intermediate
louloulinlouloulin
19

git-workflow-assistant

Guide Git branching models, PR processes, and release strategies.

Community
Basic