sync-configs

Detect cross-platform configuration drift and symlink integrity issues across Manifest deployments.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/ReefBytes-Owner/Manifest --skill sync-configs-reefbytes-owner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-configs
Source: https://github.com/ReefBytes-Owner/Manifest/tree/main/configs/claude/skills/sync-configs
Command: npx skills add https://github.com/ReefBytes-Owner/Manifest --skill sync-configs-reefbytes-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-platform config drift and symlink integrity checks for the Manifest deployment, ensuring canonical and per-platform directories stay aligned.

Core Features & Use Cases

  • Symlink integrity verification across Cursor, Gemini, and Codex targets.
  • Cross-platform configuration drift detection between .claude/ and platform-specific directories.
  • Automated reporting of broken links, missing files, and divergences for audit trails.

Quick Start

Audit the repository for drift by running the sync-configs workflow to generate a drift 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 cross-platform configuration drift in my deployment manifest?

To detect cross-platform configuration drift, you can audit canonical .claude sources against platform-specific directories to identify missing files, broken links, and divergences. This generates a structured drift report for your audit trail.

How do I verify symlink integrity across Cursor, Gemini, and Codex environments?

Symlink integrity verification checks links across Cursor, Gemini, and Codex targets by validating canonical directories. The process flags broken links and missing files, ensuring your cross-platform configuration stays aligned.

What is configuration drift detection and when do I need it for MCP configuration consistency?

Configuration drift detection identifies divergences between canonical sources and platform-specific directories. You need it for MCP configuration consistency when validating deployment manifests across multiple environments to prevent broken links.

Can I audit .claude sources against multiple platform directories simultaneously?

Yes, you can audit canonical .claude sources against platform-specific directories simultaneously. The inspection validates repository structure across Claude, Cursor, Gemini, and Codex environments to flag configuration divergences.

What is the best way to generate a structured drift report for symlink integrity audits?

The best way to generate a structured drift report is by running an automated workflow that inspects repository structure and validates symlink integrity. This flags broken links, missing files, and configuration divergences for audit trails.