branch-manager

Automates GitHub Flow branch and remote management with naming conventions.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tygwan/ultra-codex-init --skill branch-manager-tygwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-manager
Source: https://github.com/tygwan/ultra-codex-init/tree/main/.codex/skills/branch-manager
Command: npx skills add https://github.com/tygwan/ultra-codex-init --skill branch-manager-tygwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to keep branches in sync and manage remotes efficiently within GitHub Flow, causing confusion and slow collaboration.

Core Features & Use Cases

  • Create, rename, and delete branches following a clear naming convention.
  • Analyze branch activity to identify stale or long-running branches and coordinate cleanups.
  • Manage remotes (add, remove, update) and synchronize with upstreams for coordinated releases.
  • Provide guidance on merge strategies and branch lifecycle workflows in collaborative projects.

Quick Start

Create a new feature branch named feature/login-system from main and push it to origin.

Frequently Asked Questions about branch-manager

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

FAQPage Schema
How do I create and push a new feature branch in a GitHub Flow project?

To create and push a feature branch using GitHub Flow, you can automate the process from main with enforced naming conventions and push it directly to origin for remote synchronization.

What is the best way to manage stale git branches in a collaborative workflow?

Managing stale git branches involves analyzing branch activity to identify long-running branches, allowing you to coordinate cleanups and enforce lifecycle workflows in collaborative projects.

How do I synchronize local branches with upstream remotes for a coordinated release?

To synchronize local branches with upstream remotes, you can manage remote configurations by adding, removing, or updating them, ensuring coordinated releases stay aligned with the upstream repository.

Does this branch management approach enforce specific naming conventions for git branches?

Yes, this branch management approach enforces deterministic naming conventions when creating or renaming branches, ensuring consistent structure across feature, release, and main branches within your repository.

Can I get merge strategy guidance for branch lifecycles in remote management?

Yes, you can receive guidance on merge strategies and branch lifecycle workflows, helping teams coordinate merges and maintain remote synchronization without confusion during daily development.

Why do teams struggle to keep git branches in sync during GitHub Flow?

Teams struggle to keep git branches in sync during GitHub Flow due to inefficient remote management and缺乏 clear merge strategies, causing slow collaboration and confusion across remote repositories.