create-feature-branch

The create-feature-branch skill automates the process of creating a properly named feature branch from the development branch while ensuring remote tracking is correctly configured. It addresses common issues in collaborative Git workflows, such as inconsistent branch naming, outdated base branches, and missing upstream configuration. By enforcing WescoBar naming conventions and synchronizing with the latest development state before branch creation, this skill helps maintain repository hygiene and reduces integration conflicts later in the development lifecycle.

The skill validates required inputs, ensuring the issue number is present and numeric before proceeding. It generates a branch name using the required format `feature/issue-<NUMBER>-<short-description>`, optionally deriving a kebab-case description from a provided issue title. It checks for existing local and remote branches to prevent accidental duplication and provides options for handling conflicts, including checking out, renaming, or recreating branches. Before creating a new branch, it synchronizes the local development branch with the remote repository to ensure an up-to-date base. Finally, it creates the feature branch, pushes it to the remote repository, and configures upstream tracking for seamless future pulls and pushes.

This skill is intended for developers working within WescoBar workflows, particularly during Conductor workflow Phase 2, Step 1 (Branch Setup). It is useful when starting new feature implementation, picking up a GitHub issue, or initiating structured feature development. Teams that rely on consistent Git practices, issue-linked branch naming, and remote tracking will benefit from the standardized and repeatable setup process this skill provides.