submodule-dev-flow

Orchestrate parallel submodule development with per-feature worktrees and pointer bumps.

10|Updated Nov 29, 2025

Search Tags:#workflow #submodule #version-control #git-worktree #parallel-development #PRs

Ready to run

npx skills add https://github.com/benjaminshafii/digital-empire --skill submodule-dev-flow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: submodule-dev-flow
Source: https://github.com/benjaminshafii/digital-empire/tree/main/.opencode/skill/submodule-dev-flow
Command: npx skills add https://github.com/benjaminshafii/digital-empire --skill submodule-dev-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines parallel development across multiple submodules by preventing Git submodule checkout collisions and maintaining a clean master in the control-center while feature work proceeds in dedicated worktrees.

Core Features & Use Cases

Isolated feature work in submodule worktrees under worktrees/
Pinned submodule checkouts under vendor/<name> are treated as read-only
Submodule PRs merge first; then control-center bumps submodule pointers on master
Supports multi-feature development by creating per-feature worktrees and a centralized sync flow

Quick Start

Use the @submodule-dev-flow tag in prompts to enable the workflow. Follow the Standard Flow: sync master, create worktree, install dependencies and run checks, commit/push, open PR, bump pointer.

Frequently Asked Questions about submodule-dev-flow

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

FAQPage Schema

How do I prevent Git submodule checkout collisions during parallel development?▼

Preventing Git submodule checkout collisions involves isolating feature work in per-feature worktrees while keeping the main submodule checkout under vendor read-only. Merge submodule PRs first, then bump pointers on master.

What is the standard workflow for parallel multi-submodule development with worktrees?▼

Parallel multi-submodule development workflow follows these steps: sync master, create a per-feature worktree, install dependencies and run checks, commit and push, open a PR, then bump the submodule pointer on master.

Can I use Git worktrees to manage multiple submodule features simultaneously?▼

Yes, you can use Git worktrees to manage multiple submodule features simultaneously by creating a dedicated worktree for each feature. This isolates changes and maintains a clean master in the control-center repository.

When should I bump submodule pointers on master in a parallel development flow?▼

You should bump submodule pointers on master only after the corresponding submodule PRs have been successfully merged. This enforces a deterministic workflow and keeps the control-center master branch clean.

Why does my submodule checkout break when switching between feature branches?▼

Submodule checkouts break when switching branches due to Git collision conflicts. Using a pinned, read-only submodule checkout under vendor and separate worktrees for feature work prevents these collisions.