sync-configs

Audit configuration drift and symlink integrity across Claude, Cursor, Gemini, and Codex deployments.

1|Updated Aug 16, 2025

Search Tags:#validation #audit #cross-platform #config #drift #symlink

Ready to run

npx skills add https://github.com/RB-chrismandich/Manifest --skill sync-configs-rb-chrismandich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-configs
Source: https://github.com/RB-chrismandich/Manifest/tree/main/configs/claude/skills/sync-configs
Command: npx skills add https://github.com/RB-chrismandich/Manifest --skill sync-configs-rb-chrismandich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform config drift and symlink integrity across Claude, Cursor, Gemini, and Codex deployments.

Core Features & Use Cases

Audit canonical config sources against per-platform copies to detect drift and broken symlinks.
Validate symlinks, MCP server parity, and cross-platform config freshness; produce actionable reports.
Provide remediation guidance for mismatched configurations and unexpected divergences.

Quick Start

Run a baseline drift audit to generate a cross-platform configuration report.

Frequently Asked Questions about sync-configs

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

FAQPage Schema

How do I detect configuration drift across Claude, Cursor, Gemini, and Codex deployments?▼

To detect configuration drift across Claude, Cursor, Gemini, and Codex deployments, audit canonical config sources against per-platform copies to identify divergences in MCP server configurations and platform-specific files.

What is cross-platform config drift and when does it happen?▼

Cross-platform config drift occurs when platform-specific configuration copies diverge from the canonical source, causing inconsistencies across Claude, Cursor, Gemini, and Codex deployments and risking broken symlinks.

How do I validate symlink integrity for cross-platform configurations?▼

Validate symlink integrity by running deterministic checks that audit canonical sources against platform-specific copies, detecting broken symlinks and flagging divergences in MCP server configurations.

How do I check MCP server configuration parity across multiple platforms?▼

Check MCP server configuration parity by auditing canonical config sources against per-platform copies, enforcing deterministic checks for command parity and config freshness to produce structured remediation reports.

What is the best way to generate a remediation report for mismatched configurations?▼

The best way to generate a remediation report for mismatched configurations is running a baseline drift audit that enforces deterministic checks for symlink integrity, drift, and command parity across deployments.

Can I audit config freshness for Claude and Cursor deployments without external dependencies?▼

Yes, you can audit config freshness for Claude and Cursor deployments without external dependencies by running deterministic checks that validate cross-platform configuration consistency and symlink integrity.