git-workflow

Manage Git worktrees and PRs with a dev-first branching model.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill git-workflow-jonnymuir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/git-workflow
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill git-workflow-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves coordination friction in multi-issue development by enforcing a strict dev-first branching model and providing a systematic approach to parallel work using Git worktrees.

Core Features & Use Cases

  • Squad Branching Model: Ensures all feature work originates from a stable dev branch, preventing main branch pollution.
  • Parallel Worktrees: Allows developers to manage multiple simultaneous issues in the same repository without filesystem collisions or branch-switching overhead.
  • Multi-Repo Coordination: Provides a clear strategy for managing dependencies across multiple repositories using local linking and coordinated PRs.

Quick Start

Use the git-workflow skill to initialize a new worktree for issue 195 by running the worktree add command from your main repository directory.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I use Git worktrees to manage multiple issues in the same repository?

Git worktrees allow developers to manage multiple simultaneous issues in a single repository without filesystem collisions or branch-switching overhead. This skill standardizes worktree lifecycle tasks to facilitate parallel development while maintaining clean integration paths to the main branch.

What is a dev-first branching model and when do I need it for version control?

A dev-first branching model ensures all feature work originates from a stable dev branch, preventing main branch pollution. You need this structured approach when coordinating multi-issue development to resolve team coordination friction and maintain a clean integration path.

Do I need the GitHub CLI to manage Git worktrees and branch creation?

Yes, managing worktrees and branch creation with this workflow requires the GitHub CLI and standard Git utilities. These dependencies are necessary to execute structured dev-first branching operations, PR management, and worktree lifecycle tasks.

What's the best way to coordinate dependencies across multiple repositories using Git?

Multi-repo coordination is handled using local linking and coordinated PRs. This approach provides a clear strategy for managing dependencies across multiple repositories while maintaining a strict dev-first branching model.

How do I initialize a new worktree for a specific issue from my main repository?

To initialize a new worktree for a specific issue, run the worktree add command from your main repository directory. This systematically sets up a parallel development environment for that issue without filesystem collisions.