github-branches

You create a Git feature branch by using this Skill to automatically fetch remote changes, enforce naming conventions like 'claude/123-new-feature', and push the new branch to origin with upstream tracking enabled.

Managing Git branch naming conventions is handled by enforcing policies that structure branch names systematically, such as prefixing feature branches with 'claude/' followed by an issue number and description to maintain repository hygiene and organization.

Yes, you can fetch remote changes and push a new branch with upstream tracking in one workflow, as this Skill supports fetching remote updates from main and pushing newly created branches to the remote repository with upstream tracking configured.

This Git branching workflow enforces safe repository hygiene practices by applying policies for safe branching, ensuring feature branches are created from an updated main, and maintaining consistent naming conventions to keep the repository organized.

You should use a specific branching convention for Git feature branches to streamline feature development organization, ensure safe branching practices, and maintain repository hygiene by systematically naming and tracking branches like 'claude/123-fix-login-bug'.

You switch and manage Git branches efficiently by using this Skill to streamline the creation and switching process, fetching remote changes, and pushing branches to remote repositories while following team conventions and safe branching policies.