git-workflow

Implements a dev-first branching model with worktrees and multi-repo coordination for Git workflows.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill git-workflow-elbruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/git-workflow
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill git-workflow-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working on multiple issues simultaneously often struggle with branch chaos, PRs targeting the wrong base branch, and filesystem collisions when agents or developers work in parallel. This Skill enforces a consistent three-branch model (main, dev, insiders) with clear rules for branching, PRs, and cleanup. ## Core Features & Use Cases - Dev-First Branching Model: All feature work branches from dev using the squad/{issue-number}-{slug} naming convention, with draft PRs targeting dev and automated preview/insiders npm publishing. - Parallel Work with Git Worktrees: Create isolated worktrees per issue so multiple agents or developers can work simultaneously without branch switching or filesystem conflicts. - Multi-Repo Coordination: Clone downstream repos as siblings, link PRs across repositories, and use local linking (npm link, go replace, pip install -e) for cross-repo testing. - Use Case: A coordinator assigns three bug fixes at once. Each agent creates its own worktree from dev, commits on its own squad/{number}-{slug} branch, opens a draft PR to dev, and cleans up the worktree after merge. ## Quick Start Ask the AI to create a new issue branch from dev following the squad naming convention and open a draft PR targeting dev.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I work on multiple Git issues in parallel?▼

Use git worktree to create an isolated working directory per issue, each on its own branch from dev. Each worktree shares the same .git object store, so agents can commit, test, and push independently without branch switching or filesystem collisions.

How to create a draft PR targeting a dev branch with GitHub CLI?▼

Run gh pr create with --base dev, a title, a body referencing the issue such as "Closes #42", and the --draft flag. Once the work is pushed and ready, mark it with gh pr ready.

What is the difference between git worktree and cloning a repo twice?▼

Git worktree creates additional working directories that share one .git object store, making it disk-efficient for parallel branches in the same repo. Separate clones are better for cross-repo work where each repository has its own remote and history.

Can I use npm link to test changes across multiple repositories?▼

Yes, run npm link in the dependency repo and npm link <package> in the consumer repo to test cross-repo changes locally. Remove the links before committing, since CI must use published packages or PR-specific refs.

When should I not use git worktrees?▼

Avoid worktrees for single-issue work where the standard branch workflow suffices, and for cross-repo work where separate clones are required. Also clean up stale worktrees immediately after PR merge to prevent metadata drift.