skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

git-workflow

Standardize issue-based Git branching and PR workflows across dev, main, and insiders channels.

209|27|Updated Mar 10, 2026
Search Tags:#git#worktree#pull requests#branching strategy#release workflow#squad conventions#npm tags
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill git-workflow-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/git-workflow
Command: npx skills add https://github.com/dotnet/maui-labs --skill git-workflow-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy branching and mis-targeted PRs by standardizing how squads create, label, merge, and clean up issue branches in a dev-first Git workflow.

Core Features & Use Cases

  • Dev-first integration: Ensures all feature work branches from dev (never main) and are merged back through PRs.
  • Predictable release channels: Defines how main (released/tagged), dev (preview), and insiders (early-access) publish with distinct npm tags.
  • Consistent branch hygiene: Enforces issue branch naming (squad/{issue-number}-{kebab-case-slug}), provides work-in-progress labeling, and includes cleanup steps after merge.
  • Parallel work without collisions: Uses git worktree to run multiple issue agents concurrently in isolated working directories.

Quick Start

Ask your team assistant to generate an issue branch plan that targets dev, uses the required squad/{issue-number}-{slug} naming, creates a draft PR, and outlines worktree-based parallelism if multiple issues are active.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I standardize git branching and pull request workflows for a dev-first squad?▼

Standardize a dev-first git workflow by enforcing issue-based branch naming, requiring PRs to target the dev branch, applying work-in-progress labels, and executing safe cleanup procedures after merges to reduce friction.

How do I use git worktrees to run multiple issue branches in parallel?▼

Use git worktree to create isolated working directories for multiple issue branches, allowing concurrent execution of feature work without collisions before merging back to dev through pull requests.

What npm tags should I use for publishing across main, dev, and insiders release channels?▼

Use distinct npm tags for each release channel: tag main for stable releases, dev for preview builds, and insiders for early-access versions, ensuring insiders sync and publish tagging rules are maintained.

Why should feature work branch from dev instead of main in a release workflow?▼

Branching feature work from dev prevents mis-targeted PRs to main, keeping main reserved for tagged stable releases while dev integrates preview changes and reduces merge friction across squad conventions.

What is the correct branch naming convention for issue-based git workflows?▼

The correct branch naming convention is squad/{issue-number}-{kebab-case-slug}, which maintains branch hygiene and aligns pull requests with specific issues before safe cleanup after merging.

Related Skills

Explore More Software Engineering Skills→
nicolehaugennicolehaugen

git-workflow

Implements a three-branch Git workflow with naming conventions and worktrees for parallel issues.

Community
Intermediate
Golnaz89Golnaz89

git-workflow

Enforce a dev-first three-branch Git model with insiders preview.

Community
Advanced
Svenja-devSvenja-dev
38

code-quality-gate

Enforce automated quality checks across pre-commit, CI, preview, E2E, and production stages.

Community
Advanced
Jonathan0823Jonathan0823
7

git-team-workflow

Guide Git branching, commits, and PR reviews for team workflows.

Community
Basic