node-sync-prs

Port merged operator changes to Cogni node repositories as per-repo PRs.

4|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill node-sync-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-sync-prs
Source: https://github.com/cogni-dao/cogni/tree/main/.agents/skills/node-sync-prs
Command: npx skills add https://github.com/cogni-dao/cogni --skill node-sync-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propagate merged operator changes to every Cogni node repository that carries its own copy of shared code, ensuring consistency across node templates when upstream changes drift between repos.

Core Features & Use Cases

  • Per-node PR propagation: port an upstream change as one PR per repository to keep each node in sync.
  • Auditable lifecycle: maintain a ledger of branches and PRs to enable re-runs and audits.
  • Targeted edits over drift: apply changes in the most stable blocks rather than wholesale file copies, minimizing conflicts.
  • Use Case: when the operator standard updates a shared substrate, run this to port the update across all node repos.

Quick Start

Port an upstream change to all node repositories by enumerating targets, creating per-repo PRs, and validating results.

Frequently Asked Questions about node-sync-prs

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

FAQPage Schema
How do I sync a merged change across multiple GitHub repositories that share the same code?

To sync a merged change across multiple GitHub repositories, you propagate the upstream operator change by enumerating target node repos, creating one PR per repository, and validating results to maintain an auditable ledger of branches and PRs.

What's the best way to propagate upstream changes to node repos without causing wholesale file conflicts?

Propagating upstream changes to node repos is best handled by applying targeted edits in the most stable code blocks rather than wholesale file copies, minimizing conflicts while keeping each node repository in sync with the shared substrate.

When do I need to create per-repo PRs for shared code updates?

You need to create per-repo PRs for shared code updates when the operator standard updates a shared substrate and the upstream changes have drifted between multiple node repositories that each carry their own copy of the code.

Do I need GitHub access to automate syncing PRs across node repositories?

Yes, you need GitHub access and permissions to create PRs and track progress in the node repositories, as the automation requires creating individual per-repo PRs and validating results to maintain an auditable ledger.

Can I re-run or audit node repository syncs after propagating operator changes?

Yes, you can re-run and audit node repository syncs because the automation maintains an auditable ledger of branches and PRs, enabling re-runs and audits to ensure consistency across all node templates.