rc-branch-create

Create identical Git branches across a repository and its submodules.

Updated Apr 10, 2026

Search Tags:#automation #git #workflow #branching #repository #submodule

Ready to run

npx skills add https://github.com/Room-C/ai-dev-workflow --skill rc-branch-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rc-branch-create
Source: https://github.com/Room-C/ai-dev-workflow/tree/main/skills/branch-create
Command: npx skills add https://github.com/Room-C/ai-dev-workflow --skill rc-branch-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the manual overhead and risk of inconsistency when creating identical feature branches across a main repository and multiple nested Git submodules.

Core Features & Use Cases

Atomic Branching: Automatically creates the same branch name in the root repository and all initialized submodules.
Safety Guardrails: Validates workspace cleanliness and prevents branch creation if conflicts exist or if the base branch is missing.
Use Case: When starting a new feature that spans multiple microservices managed as submodules, use this skill to ensure all repositories are aligned on the same base branch and ready for development simultaneously.

Quick Start

Use the rc-branch-create skill to create a new branch named feature/login-update based on the develop branch.

Frequently Asked Questions about rc-branch-create

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

FAQPage Schema

How do I create the same git branch across a repository and all its submodules?▼

To create the same git branch across a repository and all its submodules, you can automate the process using atomic checkout operations. This ensures all nested repositories align on the identical branch name simultaneously.

Why does creating a feature branch fail when my workspace has uncommitted changes?▼

Creating a feature branch fails with uncommitted changes due to safety guardrails that validate workspace cleanliness. This prevents branch creation if conflicts exist, ensuring repository consistency across submodules.

What is the best way to manage synchronized branching for multi-repository development?▼

Synchronized branching for multi-repository development is best managed by automating identical branch creation across a primary repository and configured submodules. This aligns microservices on the same base branch for simultaneous development.

Do I need bash to automate branch creation across multiple git submodules?▼

Yes, you need bash, git, and standard Unix utilities to automate branch creation across multiple submodules. These tools perform the atomic checkout and branch operations required for the workflow.

Can I prevent branch creation if the base branch is missing in a submodule?▼

Yes, you can prevent branch creation if the base branch is missing by using safety guardrails. The automation validates workspace cleanliness and stops the process if the base branch is absent or conflicts exist.