sync-change

Align pipeline documentation after structural changes to stages or outputs.

Updated Mar 8, 2026

Search Tags:#automation #documentation #consistency #validation #synchronization #pipeline #contradictions

Ready to run

npx skills add https://github.com/DamarisDeng/paper-writing-system --skill sync-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-change
Source: https://github.com/DamarisDeng/paper-writing-system/tree/main/.claude/skills/sync-change
Command: npx skills add https://github.com/DamarisDeng/paper-writing-system --skill sync-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes documentation alignment across the pipeline after non-trivial changes to stage structure, data flow, or outputs.

Core Features & Use Cases

Ensures README.md, orchestrator frontmatter, and progress utilities stay consistent after renames, renumbering, or folder changes.
Detects non-trivial contradictions across sources and proposes resolution options to minimize drift.
Guides manual resolution and optional contradiction checks to maintain a single source of truth.

Quick Start

Run the sync-change command to align all pipeline documentation after structural updates.

Frequently Asked Questions about sync-change

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

FAQPage Schema

How do I keep pipeline documentation consistent after renaming or renumbering stages?▼

To keep pipeline documentation consistent after structural changes, you can run an automated synchronization process that aligns README.md, orchestrator SKILL.md, and progress_utils.py. This prevents drift and ensures all references stay aligned across your pipeline files.

What is the best way to resolve contradictions across pipeline documentation files?▼

Resolving contradictions across pipeline documentation requires detecting inconsistencies between sources and proposing actionable resolution options. This minimizes drift and guides manual resolution to maintain a single source of truth across files.

How do I synchronize orchestrator frontmatter and progress utilities after adding new pipeline stages?▼

To synchronize orchestrator frontmatter and progress utilities after adding or removing stages, apply an automated documentation alignment process. This enforces correct progress_utils.py API usage and checks for contradictions across the updated outputs.

Does automated documentation alignment work for changes to output folders and skill frontmatter?▼

Yes, automated documentation alignment works for changes to output folders and skill frontmatter. It synchronizes these structural updates across README.md and orchestrator files, checking for contradictions and surfacing actionable resolutions to maintain consistency.

When should I run documentation synchronization for my pipeline?▼

You should run documentation synchronization after making non-trivial structural changes to your pipeline, such as stage renumbering, renaming, adding or removing stages, and modifying output folders. This ensures all tracked files remain in sync.