git-branch Skill
Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge). Published by microsoft in devsquad-copilot.
Decision snapshot
Is this a fit?
Developers using devsquad-copilot, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
3 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is git-branch Skill?
Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge). Published by microsoft in devsquad-copilot. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using devsquad-copilot
Declared skill metadata
- Source file: .github/plugins/devsquad/skills/git-branch/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use git-branch Skill
- Use it for developers using devsquad-copilot.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/git-branch/SKILL.md
What it does
Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge).
Skill instructions
Git Branch — Branch Management Check Branching Strategy Config bash 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: bash git branch --show-current git status git fetch origin Remote Synchronization If on main/master/develop, check synchronization: bash 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
Verified compatibility and discovery
Frequently asked questions
What is git-branch?
git-branch is a open-source AI agent skill with Copy skill directory. Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code.
Who is git-branch best for?
git-branch is best for reusing agent instructions, scripts, and references.
How do I install git-branch?
Install or run git-branch using Copy skill directory. Check git-branch for the latest setup command.
Is git-branch actively maintained?
git-branch may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
