config-sync-cli-workflow

Orchestrate multi-target CLI configuration synchronization with phase-driven workflows and backups.

10|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/CsHeng/dot-claude --skill config-sync-cli-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-sync-cli-workflow
Source: https://github.com/CsHeng/dot-claude/tree/main/.claude/skills/config-sync-cli-workflow
Command: npx skills add https://github.com/CsHeng/dot-claude --skill config-sync-cli-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate the multi-target CLI configuration synchronization using phase runners and planners, ensuring backups and auditability.

Core Features & Use Cases

  • Phase Pipeline: Collect, analyze, plan, prepare, adapt, execute, verify, cleanup, and report.
  • Backup-First Execution: Normalize parameters, back up before writes, and enforce phase ordering.

Quick Start

Run the CLI sync workflow across CLI targets, e.g.: /config-sync/sync-cli --action=sync-all

Frequently Asked Questions about config-sync-cli-workflow

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

FAQPage Schema
How do I synchronize CLI configuration across multiple targets?

CLI configuration synchronization across multiple targets uses phase-driven workflows that normalize parameters, back up configurations before writes, and enforce ordered execution. This Skill orchestrates the entire process with plan generation, audit trails, and permission checks across diverse environments.

What phases does a multi-target config-sync workflow follow?

The workflow follows nine ordered phases: collect, analyze, plan, prepare, adapt, execute, verify, cleanup, and report. Each phase enforces strict sequencing to ensure parameters normalize against settings.json, backups complete before writes, and all changes remain auditable.

Can I back up configurations before applying CLI changes?

Yes. Pre-write backups are enforced as a core feature—configurations are backed up before any write operation occurs. The Skill also persists plans, logs, and metadata throughout execution for complete auditability and recovery capability.

How do I ensure CLI parameter consistency across environments?

Parameter normalization against settings.json standardizes configurations across all CLI targets. The Skill validates and normalizes parameters during the collect and analyze phases before plan generation, ensuring consistency before execution begins.

What happens if a config-sync phase fails or needs to be repeated?

Enforced phase ordering prevents out-of-sequence execution. Plans, logs, and metadata persist throughout the workflow, enabling you to audit what failed, review the execution record, and retry from a known state with full context.

Do I need specific permissions to execute configuration sync across targets?

Yes. Permission checks are enforced before writes occur as part of the prepare phase. The Skill validates that necessary permissions exist across all target environments before any configuration changes are applied.