dual-remote-push

Pushes the current Git branch to both upstream and origin remotes on demand.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bakwankawa/lazy-code-skill --skill dual-remote-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dual-remote-push
Source: https://github.com/bakwankawa/lazy-code-skill/tree/main/.cursor/skills/lazy-code-skill/dual-remote-push
Command: npx skills add https://github.com/bakwankawa/lazy-code-skill --skill dual-remote-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of pushing the current Git branch to two remotes (upstream corporate and origin internal), ensuring your activity is mirrored across both repositories for visibility and backup.

Core Features & Use Cases

  • On-demand dual-remote push: Pushes the same branch to both remotes in a single operation.
  • Safe and explicit: Only runs when explicitly invoked and relies on pre-configured remotes named upstream and origin.
  • Use Case: When you need to keep your corporate repo and internal/internal-facing repo synchronized without per-remote commands.

Quick Start

Run the command to push the current branch to both remotes: git push upstream <branch> && git push origin <branch>

Frequently Asked Questions about dual-remote-push

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

FAQPage Schema
How do I push a git branch to two remotes at the same time?

To push a git branch to two remotes simultaneously, you run a combined command pushing the current branch to both upstream and origin. This executes sequential git push commands for upstream corporate and origin internal remotes in a single operation.

What is dual-remote synchronization in a git workflow?

Dual-remote synchronization is the process of mirroring commits to both a corporate upstream and an internal origin repository. It ensures your branch activity remains visible and backed up across both remote repositories without requiring separate manual push commands.

Do I need to configure specific remote names to use this dual push?

Yes, you need pre-configured remote repositories named upstream and origin. The Skill relies on these explicit remote names to execute standard git push commands against the corporate upstream and internal origin remotes.

Can I push both feature branches and main branches to multiple remotes?

Yes, you can push both feature branches and main branches to multiple remotes. The Skill pushes the current branch on demand to both upstream and origin, applying dual-remote synchronization across any active branch you invoke it on.

Is there a way to automate mirroring commits to a corporate upstream and internal origin?

Mirroring commits to a corporate upstream and internal origin is automated by invoking this Skill on demand. It executes a chained git push command to both remotes, keeping repositories synchronized without per-remote manual input.

Why does my dual-remote push require explicit invocation?

Your dual-remote push requires explicit invocation to ensure safe and controlled execution. The Skill only runs when directly called by the user, preventing accidental pushes to the corporate upstream or internal origin remotes.