custom-multi-repo-push

To commit and push changes to multiple git repositories, this skill automates coordinated batch updates across several repos. It generates a preflight plan of git commands, requires your explicit consent, and then executes the pushes with action logging for safety.

The safest way to automate batch git commits is using a plan-driven execution workflow. This skill enforces preflight plan generation and explicit user consent before running any commands, ensuring transparency and preventing unauthorized operations across your repositories.

No, you cannot execute multi-repo git pushes without confirmation. The skill enforces explicit user consent after generating the preflight plan, ensuring you review and approve all batch update commands before they are applied to your repositories.

To stage and push planned changes across monorepos and polyrepos, run the multi-repo push workflow. The skill applies batch updates to multiple repositories simultaneously while maintaining action logging for auditing and operational safety.

Yes, the multi-repo push workflow tracks executed git commands for auditing. It enforces action logging after you provide explicit consent, ensuring all batch updates propagated across your repositories are fully traceable.

You need an automated multi-repo push solution when managing development workflows across several repositories like monorepos or polyrepos. It is necessary when batch updates must be propagated simultaneously to simplify cross-repository code synchronization and release processes.