$ ~/registry/skill/microsoft-github-plugins-devsquad-skills-git-branch

SKILL

git-branch

Name: git-branch
Author: microsoft

Create, switch, and verify Git branches before starting implementation work.

Stars

★ 36

Source

GitHub

Updated

2026-07-05

// securityCaution

Prompt only, no code
Open source

Summary

This is an open-source, prompt-only Git branch management skill with no stated secrets or external endpoints, so the overall risk is low. Its instructions reference local git commands and reading a repo-local config file, which are normal development-assistance behaviors and mainly require using it only in the intended repository context.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required, and the README does not ask for tokens, accounts, or other sensitive credentials. No clear credential leakage or abuse path is evident.

Network egressLow risk

No remote endpoints are declared. The documentation mentions `git fetch origin` and checking `origin/<branch>`, but that is standard synchronization with the repository's existing Git remote rather than an extra unknown service. There is no sign of sending data to unrelated third-party endpoints.

Code executionLow risk

The system flags it as prompt-only, meaning it is not itself an executable tool. The `git` and `cat` commands in the README are operational guidance for the model or user, not built-in local code-execution capability provided by the skill itself.

Data accessLow risk

The material only involves reading the current repository state and a repo-local `.memory/git-config.md`, plus branch switching/creation as Git metadata operations. It does not show broad system file access, cross-project data access, or excessive permissions.

Supply chainCaution

The source is an open GitHub repository associated with Microsoft, and the code is auditable, which are positive signals. However, the license is undeclared, stars are 0, and maintenance status is unknown, so community validation and ongoing support signals are weak; review the repository contents before adoption.

Recommendations

Verify that the repository source matches the README and that it only provides prompt templates without extra automation behavior.
If following commands like `git fetch origin`, first confirm that the current repository remote points to the expected organization and project.
Use this skill only within the intended code repository to avoid applying its suggested steps in unrelated directories containing sensitive content.
Review the repository license, commit history, and maintenance activity before adopting it into a team-standard toolchain.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "git-branch" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/git-branch/SKILL.md
2. Save it as ~/.claude/skills/git-branch/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Create a feature branch

Prompt

Create a new branch named feature/login-page from main and switch to it.

Expected

Provides the Git command or steps to create and switch to the branch.

Check current branch status

Prompt

Show me how to check the current branch and list all local branches.

Expected

Provides commands to see the current branch and list local branches.

Verify branching strategy

Prompt

I need to fix a production hotfix bug. Help me confirm which branch to branch from and explain why.

Expected

Suggests the correct base branch, branch naming, and a brief strategy explanation.

// docs

Git Branch — Branch Management

Check Branching Strategy Config

cat .memory/git-config.md 2>/dev/null

If Branching Strategy is filled in, use the configured strategy. The detect-branching-strategy.sh hook automatically seeds on sessionStart.

If the config has Confidence: medium, confirm with the dev before using (see Detect Branching Strategy section).

Check Git State

Before starting implementation:

git branch --show-current
git status
git fetch origin

Remote Synchronization

If on main/master/develop, check synchronization:

git rev-list HEAD..origin/<branch> --count

Situation	Action
Branch behind (commits behind remote)	Alert and suggest pull
Branch with uncommitted local changes	Alert about pending changes
Branch up to date and clean	Proceed normally

If the main branch is behind:

Your branch [main] is [N] commits behind the remote.

I recommend updating before creating a new branch:

[P] Pull and continue
[I] Ignore and continue anyway (not recommended)
[A] Abort implementation

Evaluate Situation for Branch Creation

Situation	Action
Already on a feature branch (not main/master/develop)	Use current branch
On main/master/develop without changes with work item	Create branch automatically (see below)
On main/master/develop without changes without work item	Ask if they want to create a branch
On main/master/develop with changes	Alert and ask how to proceed

Automatic Creation (when there is a work item)

When the source of work is a GitHub issue or Azure DevOps work item, create the branch automatically.

Naming convention:

feature/<id>-<short-description>

Rules for <short-description>:

Derived from the work item title
Lowercase letters, numbers, and hyphens only
Maximum 50 characters in the total branch name
Remove articles, prepositions, and unnecessary words

Examples:

Work Item	Branch
#42 "Implement user authentication"	`feature/42-user-authentication`
#108 "Add rate limiting to API endpoints"	`feature/108-rate-limiting-api`
WI 5678 "Create financial reports endpoint"	`feature/5678-financial-reports-endpoint`

Action: Create branch and inform the user:

Branch created: feature/<id>-<short-description>

[C] Continue with this branch
[R] Rename branch: _

The user can rename, but the flow does not block waiting for confirmation to create.

Interactive Creation (without work item)

When the source is tasks.md (without issue/work item), ask the user:

You are on the main branch. Do you want me to create a branch for this implementation?

Suggestion: feature/<short-description>

[S] Yes, create suggested branch
[N] No, continue on current branch
[C] Create with another name: _

Existing Branch

If the user is already on a feature branch, use the current branch without additional questions.

Detect Branching Strategy

When .memory/git-config.md does not exist or does not have Branching Strategy, detect automatically:

# 1. Default branch
DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@')

# 2. Does develop branch exist?
HAS_DEVELOP=$(git ls-remote --heads origin develop 2>/dev/null | grep -q develop && echo "yes" || echo "no")

# 3. Do release/* or hotfix/* branches exist? (GitFlow pattern)
HAS_GITFLOW_BRANCHES=$(git branch -r 2>/dev/null | grep -qE '(release|hotfix)/' && echo "yes" || echo "no")