node-template-sync

Automating fork-sync PR merges requires sweeping all auto-generated pull requests, triaging per-node edge cases, and driving merges to completion. This skill handles the entire two-tier sync workflow and PR lifecycle management across all forks.

Porting node-template changes into an operator app involves hand-porting merged release changes and promoting them to production-ready branches. This skill automates sweeping fork-sync PRs and porting those changes directly into the operator app.

Conflict resolution during fork synchronization works by implementing a two-tier sync workflow that triages per-node edge cases individually. It manages the PR lifecycle across all forks to drive merges to completion despite conflicts.

You need to trigger a fork-sync workflow when node-template releases merge to main and auto-open fork-sync PRs. This skill sweeps those PRs, triages issues, and ports the same changes into the operator app.

Yes, you can use this automation to promote merged changes to production-ready branches. It maintains synchronization across forks after porting node-template changes into the operator app.

Auto-generated fork-sync PRs are not merged automatically because the operator app only opens them without merging or porting changes. This skill acts as the agent to finish the job by sweeping PRs and driving merges.