skills.rest
forcedotcom
forcedotcomOFFICIAL
Explore all skills by this author →
Website𝕏@salesforcedevsGitHub

feature-branch

Creates Git feature branches with owner-prefixed naming to protect main and develop branches.

1.0k|454|Updated Jun 21, 2017
Search Tags:#Git#feature branch#Git Workflow#Version Control#protected branches#Branch Naming
One-click install
npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill feature-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-branch
Source: https://github.com/forcedotcom/salesforcedx-vscode/tree/main/.claude/skills/feature-branch
Command: npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill feature-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accidental commits and pushes to protected branches like develop or main can disrupt team workflows and shared repositories. This Skill enforces a consistent feature-branch workflow so all work happens on isolated, properly named branches.

Core Features & Use Cases

  • Protected Branch Enforcement: Prevents direct commits to develop or main by routing all work through feature branches.
  • Standardized Naming Convention: Generates branch names in the format <ownerPrefix>/W-XXXXX-short-description, resolving the owner prefix via the gus-cli runner identity.
  • Safe Push Configuration: Creates branches with --no-track off origin/develop so a bare git push cannot accidentally push develop.
  • Use Case: A developer starting work item W-12345 runs the workflow to fetch origin/develop, create sm/W-12345-fix-login-bug, commit changes, and push the branch upstream without risking the shared develop branch.

Quick Start

Create a new feature branch for work item W-12345 based on origin/develop and push it safely.

Frequently Asked Questions about feature-branch

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

FAQPage Schema
How do I create a Git feature branch from develop?▼

Fetch the latest develop branch, then run git checkout -b <ownerPrefix>/W-XXXXX-description origin/develop --no-track. Commit your work and push with git push -u origin followed by the branch name.

What naming convention should I use for Git feature branches?▼

Use the format <ownerPrefix>/W-XXXXX-short-description, where the owner prefix is resolved from the gus-cli runner identity. For example, a developer with prefix sm creates sm/W-12345-fix-login-bug.

Why use --no-track when branching from origin/develop?▼

The --no-track flag prevents the new branch from tracking origin/develop. Without it, a bare git push could push the shared develop branch instead of your feature branch, risking unintended changes to protected code.

Can I commit directly to the develop or main branch?▼

No, this workflow prohibits commits to develop or main. All changes must be made on a dedicated feature branch and merged through the standard review process.

How do I find my owner prefix for branch naming?▼

The owner prefix is resolved through the gus-cli runner identity, as referenced in the gus-cli skill documentation. For example, Shane McLaughlin resolves to the prefix sm.

Related Skills

Explore More Software Engineering Skills→
YoniChechikYoniChechik

create-clone

Create an isolated git clone and feature branch from a feature description.

Community
Basic
RonHoubenRonHouben
2

merge-pull-request

Merge approved GitHub pull requests via GitHub CLI after CI checks pass.

Community
Intermediate
scruffydanscruffydan

git-push

Automate pre-push verification of README, tests, linting, and secrets.

Community
Basic
hung-phanhung-phan

trunk-based-development

Implement a trunk-based development workflow with short-lived branches and feature flags.

Community
Advanced