workflow-sync-template

Sync downstream projects with upstream templates via sync-manifest.yaml.

9|Updated Feb 22, 2026

Search Tags:#automation #workflow #templates #manifest #sync #downstream

Ready to run

npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill workflow-sync-template

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-sync-template
Source: https://github.com/lhpaul/ai-dev-framework-template/tree/main/.codex/skills/workflow-sync-template
Command: npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill workflow-sync-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This primer describes a deterministic, manifest-driven workflow to keep downstream projects aligned with an upstream template, reducing drift and manual rework.

Core Features & Use Cases

Manifest-driven synchronization: reads sync-manifest.yaml from the upstream template (root) after resolving the template source and applies the authoritative file list, with a fallback to embedded lists when the manifest is absent.
Rename cleanup detection: if an entry rename_detections exists, applies the cleanup logic and surfaces the rename step in the preview when candidates are found.
Safe, user-confirmed updates: presents a structured summary of always-sync, new, modified, and up-to-date items before requiring confirmation to apply changes.

Quick Start

Run the workflow-sync-template skill to pull the latest framework files from the upstream template into this project.

Frequently Asked Questions about workflow-sync-template

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

FAQPage Schema

How do I sync upstream templates into multiple downstream projects to reduce drift?▼

Manifest-driven synchronization reads sync-manifest.yaml from the upstream template root to apply an authoritative file list, with fallback to embedded lists when the manifest is absent. This keeps downstream projects aligned and reduces drift.

What is the best way to handle rename cleanup detection during repository maintenance?▼

Rename cleanup detection during repository maintenance is handled by checking for a rename_detections entry. When found, the workflow applies cleanup logic and surfaces the rename step in a structured preview for user confirmation before applying changes.

How does manifest-driven synchronization apply changes safely without breaking configs?▼

Manifest-driven synchronization applies changes safely by presenting a structured summary of always-sync, new, modified, and up-to-date items. It requires explicit user confirmation before applying any updates to downstream projects, ensuring controlled repository maintenance.

Can I sync docs and config files across multiple projects if the upstream manifest is missing?▼

Yes, you can sync docs and config files when the upstream manifest is missing. The workflow checks for sync-manifest.yaml in the template root and automatically falls back to embedded file lists to resolve the authoritative synchronization targets.

Does workflow-sync-template require manual updates after pulling the latest framework files?▼

No, manual updates are minimized. After pulling the latest framework files from the upstream template, the workflow generates a structured summary of new and modified items and requires a single user confirmation to apply all changes across downstream projects.