source-command-sync

Verify guide repository and landing page content synchronization via check-landing-sync.sh.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/srednoff888-art/4 --skill source-command-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-sync
Source: https://github.com/srednoff888-art/4/tree/main/.agents/skills/source-command-sync
Command: npx skills add https://github.com/srednoff888-art/4 --skill source-command-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Synchronizing content between the guide repository and its public landing site to ensure consistency and up-to-date information.

Core Features & Use Cases

  • Detects and reports parity across guide files, landing index, and quizzes.
  • Automates a reproducible check using the provided check-landing-sync.sh script.
  • Generates a clear, human-readable status summary to guide remediation.

Quick Start

Run the migration sync check to verify that guide and landing content are aligned.

Frequently Asked Questions about source-command-sync

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

FAQPage Schema
How do I verify content parity between my guide repository and landing page?

Guide and landing page content parity is verified by running a deterministic check-landing-sync.sh script that compares guide files, landing index, templates, quiz questions, and codex versions to report synchronization status and guide remediation.

What is guide-to-landing content synchronization and when do I need to check it?

Guide-to-landing content synchronization ensures consistency between your repository content and its public landing site, and needs checking during migrations and ongoing updates across guide ecosystems to prevent outdated information.

How do I automate a reproducible check for guide and landing content sync?

Automate reproducible content sync checks by executing the check-landing-sync.sh script, which applies a deterministic verification process and generates a clear, human-readable status summary to guide remediation.

Does this content verification approach work for ongoing updates across guide ecosystems?

Yes, the content verification applies to checking full repository-to-landing parity across guide ecosystems for both migrations and ongoing updates, covering templates, quiz questions, and codex versions.

What's the best way to check repository-to-landing parity for guide migrations?

The best way to check repository-to-landing parity for migrations is executing a deterministic sync script that reports structured results across guide content, landing index, and quizzes to ensure status consistency.