Git Workflow
Squad branching model: dev-first workflow with insiders preview channel
Install
npx skills add Azure-Samples/agent-skills-dotnet-demo --skill git-workflowgit clone --depth 1 https://github.com/Azure-Samples/agent-skills-dotnet-demo.git /tmp/agent-skills-dotnet-demo
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills-dotnet-demo/.squad/templates/skills/git-workflow ~/.claude/skills/git-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## Context
Squad uses a three-branch model. **All feature work starts from `dev`, not `main`.**
| Branch | Purpose | Publishes |
|--------|---------|-----------|
| `main` | Released, tagged, in-npm code only | `npm publish` on tag |
| `dev` | Integration branch — all feature work lands here | `npm publish --tag preview` on merge |
| `insiders` | Early-access channel — synced from dev | `npm publish --tag insiders` on sync |
## Branch Naming Convention
Issue branches MUST use: `squad/{issue-number}-{kebab-case-slug}`
Examples:
- `squad/195-fix-version-stamp-bug`
- `squad/42-add-profile-api`
## Workflow for Issue Work
1. **Branch from dev:**
```bash
git checkout dev
git pull origin dev
git checkout -b squad/{issue-number}-{slug}
```
2. **Mark issue in-progress:**
```bash
gh issue edit {number} --add-label "status:in-progress"
```
3. **Create draft PR targeting dev:**
```bash
gh pr create --base dev --title "{description}" --body "Closes #{issue-number}" --draft
```
4. **Do the work.** Make changes, write tests, commit with issue reference.
5. **Push and mark ready:**
```bash
git push -u origin squad/{issue-number}-{slug}
gh pr ready
```
6. **After merge to dev:**
```bash
git checkout dev
git pull origin dev
git branch -d squad/{issue-number}-{slug}
git push origin --delete squad/{issue-number}-{slug}
```
## Parallel Multi-Issue Work (Worktrees)Details
- Skill name
git-workflow- Repository
- Azure-Samples/agent-skills-dotnet-demo
- Path
.squad/templates/skills/git-workflow/SKILL.md- License
- MIT
- Repo updated
- 10 April 2026
FAQ
What does the Git Workflow skill do?
Squad branching model: dev-first workflow with insiders preview channel
How do I install the Git Workflow skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Azure-Samples/agent-skills-dotnet-demo --skill git-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Git Workflow popular?
It lives in Azure-Samples/agent-skills-dotnet-demo, which has 45 GitHub stars and 11 forks.
Related skills
Agent Collaboration
45Azure-Samples/agent-skills-dotnet-demo
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Agent Conduct
45Azure-Samples/agent-skills-dotnet-demo
Shared hard rules enforced across all squad agents
Architectural Proposals
45Azure-Samples/agent-skills-dotnet-demo
How to write comprehensive architectural proposals that drive alignment before code is written
Github Multi Account
45Azure-Samples/agent-skills-dotnet-demo
Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.
Gh Auth Isolation
45Azure-Samples/agent-skills-dotnet-demo
Safely manage multiple GitHub identities (EMU + personal) in agent workflows
Whose Red
33okgrit/done-is-a-claim
Investigate whether a failing test run is caused by a change, was already broken on main, or is inconclusive, using matched branch and clean-main runs. Use when tests fail on a branch or PR, when an agent says 'this failure is pre-existing', or before retrying or reverting a fix.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.