core-runtime-sync

Mirror versioned .github assets and MCP configurations into local runtime folders.

2|1|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill core-runtime-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-runtime-sync
Source: https://github.com/ThiagoGuislotti/copilot-instructions/tree/main/.codex/skills/core-runtime-sync
Command: npx skills add https://github.com/ThiagoGuislotti/copilot-instructions --skill core-runtime-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps local runtime folders aligned with the versioned repository by mirroring central assets into the user’s environment, removing drift and configuration inconsistencies.

Core Features & Use Cases

  • Asset synchronization: Mirror the versioned .github assets and MCP-related configurations into local runtime folders for reliable development workflows.
  • Environment consistency: Ensure that local runtime folders reflect the repository state to reduce drift and misconfigurations.
  • Use Case: A developer clones a project and wants their local ~/.github and ~/.codex runtimes to match the repository's current asset state automatically.

Quick Start

Run pwsh -File scripts/runtime/bootstrap.ps1 to bootstrap the local runtime alignment with the shared assets.

Frequently Asked Questions about core-runtime-sync

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

FAQPage Schema
How do I sync local runtime folders with shared repository assets?

To sync local runtime folders, this Skill mirrors versioned .github assets and MCP configurations into your local environment, removing configuration drift. It requires running PowerShell bootstrap scripts to align your local folders with the central repository state.

Why does my local development environment have configuration drift from the main repository?

Configuration drift happens when local runtime folders are not synchronized with versioned repository assets. This Skill solves the problem by automatically mirroring central .github assets and MCP manifests into your local environment for consistency.

How do I bootstrap a local Codex runtime to match the repository state?

To bootstrap a local Codex runtime, run the command pwsh -File scripts/runtime/bootstrap.ps1. This executes the synchronization script that aligns your local ~/.github and ~/.codex runtimes with the shared versioned assets.

Do I need PowerShell to synchronize MCP manifests into local runtime environments?

Yes, you need PowerShell to execute the synchronization scripts. The Skill requires PowerShell scripts and shared MCP manifests to successfully apply versioned assets and align your local runtime environment.

What's the best way to maintain environment consistency for local replicas of shared repositories?

The best way to maintain environment consistency is to mirror versioned .github assets and MCP configurations into local runtime folders automatically. This process reduces drift and ensures local replicas reflect the current repository state reliably.

Does this runtime synchronization approach work with shared MCP configurations?

Yes, this runtime synchronization works directly with shared MCP configurations. It applies versioned MCP manifests to your local environment, ensuring your local Codex runtime remains aligned with the shared repository configurations.