submodule-push

Push submodule commits to remote forks and update parent references.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/IstoraMandiri/etc-nexus --skill submodule-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submodule-push
Source: https://github.com/IstoraMandiri/etc-nexus/tree/main/.claude/skills/submodule-push
Command: npx skills add https://github.com/IstoraMandiri/etc-nexus --skill submodule-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push submodule changes from a local submodule to its remote fork, ensuring forks stay in sync with the parent repository after development work.

Core Features & Use Cases

  • Submodule synchronization: Pushes commits from hive or core-geth submodules to their respective forks.
  • Reference retention: Keeps the submodule reference updated in the parent repo.
  • Use Case: After updating code in a submodule, push to the corresponding fork and update the parent submodule reference in the main repository.

Quick Start

Push changes from the specified submodule (hive or core-geth) to its remote fork and update the parent submodule reference.

Frequently Asked Questions about submodule-push

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

FAQPage Schema
How do I push submodule commits to a remote fork?

Pushing submodule commits to a remote fork requires navigating into the submodule, verifying pending commits, detecting the current branch, and executing git push -u origin <branch> to sync the changes.

How do I update the parent repository reference after pushing a submodule?

After pushing a submodule, the parent repository reference can be updated by returning to the parent directory and applying the optional submodule reference update to keep the main repository aligned.

How does submodule synchronization work for hive and core-geth forks?

Submodule synchronization for hive and core-geth forks works by pushing local submodule changes to their respective IstoraMandiri remote forks, ensuring the parent repository keeps an updated reference after the push.

What is the best way to keep a parent repository aligned after submodule updates?

The best way to keep a parent repository aligned after submodule updates is to push the submodule commits to its fork and then update the parent submodule reference to point to the latest commit.

Can I push local changes from a submodule directly to its remote fork?

Yes, you can push local changes from a submodule directly to its remote fork by navigating into the submodule, confirming pending commits, and running git push -u origin <branch> from the detected branch.

Why does my parent repository not reflect recent submodule commits?

Your parent repository does not reflect recent submodule commits because the submodule reference needs updating after pushing to the fork, which requires returning to the parent directory and applying the reference change.