branching

Name: branching
Availability: InStock
Author: Pandaworks

Create Git branches from local references without upstream inheritance.

Updated Mar 1, 2026

Search Tags:#git #workflow #safety #branching #naming-conventions #upstream #local-ref

Ready to run

npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill branching-pandaworks-software-plt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branching
Source: https://github.com/pandaworks-software-plt/pandahrms-skills/tree/main/skills/branching
Command: npx skills add https://github.com/pandaworks-software-plt/pandahrms-skills --skill branching-pandaworks-software-plt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ALWAYS use when the user needs to create, start, or checkout a new git branch. Prevents dangerous upstream tracking inheritance and enforces folder-based naming conventions. Triggers on any mention of new branch, new feature branch, branching off, or checkout -b

Core Features & Use Cases

Safely creates branches from local refs, ensuring no upstream inheritance
Enforces folder-based naming conventions and branch type prefixes
Warns when branching from non-main branches and guides user to confirm intent

Quick Start

Ask the user for the purpose and source branch, then propose a safe, folder-based branch name and confirm before proceeding.

Frequently Asked Questions about branching

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

FAQPage Schema

How do I create a Git branch without inheriting upstream tracking?▼

To create a Git branch without inheriting upstream tracking, you must ensure the branch originates from a local reference. This approach fetches the latest changes, checks out a local source, and creates a local branch with no upstream link, requiring explicit confirmation before the first push.

Why does my new Git branch track a remote upstream automatically?▼

Your new Git branch tracks a remote upstream automatically when it inherits tracking configuration from the source branch. To prevent this, you must create branches exclusively from local refs and verify that no upstream tracking is configured before pushing.

What is the safest workflow for branching off a non-main Git branch?▼

The safest workflow for branching off a non-main Git branch involves prompting warnings when the source is non-main and requiring explicit user confirmation of intent. This ensures you safely create feature or fix branches from local sources without unintended upstream inheritance.

How to enforce folder-based naming conventions when starting a new feature branch?▼

To enforce folder-based naming conventions when starting a new feature branch, you can apply policy-driven rules that generate safe, folder-based branch names with type prefixes. This requires asking for the branch purpose and source before proposing a name.

Can I prevent accidental upstream pushes when creating local Git feature branches?▼

Yes, you can prevent accidental upstream pushes when creating local Git feature branches by verifying no upstream is configured after branch creation. This deterministic branching step requires explicit user confirmation before proceeding with the first push.

What are the limitations of creating Git branches directly from remote tracking refs?▼

Creating Git branches directly from remote tracking refs carries the limitation of dangerous upstream tracking inheritance. This risk necessitates a workflow that checks out a local source first, ensuring no upstream is inherited and requiring confirmation before pushing.