propagator

Propagate changes across distributed systems using bash scripts and SSH commands.

1|Updated Feb 26, 2026

Search Tags:#automation #deployment #sync #change management #ecosystem #propagation

Ready to run

npx skills add https://github.com/GrazianoGuiducci/d-nd-seed --skill propagator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propagator
Source: https://github.com/GrazianoGuiducci/d-nd-seed/tree/main/plugins/d-nd-core/skills/propagator
Command: npx skills add https://github.com/GrazianoGuiducci/d-nd-seed --skill propagator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that changes made in one part of the system are correctly reflected and updated across all dependent areas, preventing inconsistencies and outdated information.

Core Features & Use Cases

Change Management: Automatically triggers updates and synchronizations based on specific change events.
Ecosystem Consistency: Maintains alignment across different components like skills, websites, and AI models.
Use Case: After updating a core skill in the d-nd-seed repository, this Skill will automatically initiate the necessary scripts to sync these changes to the THIA skill, update the d-nd.com website, and notify relevant teams.

Quick Start

Use the propagator skill to sync changes from THIA to d-nd-seed.

Frequently Asked Questions about propagator

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

FAQPage Schema

How do I automate change propagation across a distributed system after updating code?▼

Change propagation is automated by triggering bash scripts and SSH commands that sync modifications to downstream targets. This ensures dependent areas like skills, websites, and deployment sequences receive updates immediately after core code changes, preventing inconsistencies.

What is the best way to keep ecosystem components consistent when modifying a core repository?▼

Ecosystem consistency is maintained by automatically initiating synchronization scripts upon change events. After modifying a core repository, the system syncs updates to dependent components, updates website content, and notifies relevant teams to ensure alignment.

Does automated change management require SSH access to update downstream targets?▼

Yes, automated change management requires bash scripts and SSH commands to execute updates across different environments. SSH access enables the system to reach distributed downstream targets and apply necessary modifications after detecting changes.

How do I sync changes between separate development environments using bash scripts?▼

Syncing changes between environments is handled by running propagation scripts that detect modifications in a source repository and trigger SSH commands to update the downstream target. This maintains alignment across distributed system components.

Why does my website content show outdated information after updating a core skill?▼

Website content becomes outdated when change propagation fails to trigger synchronization scripts after modifying core skills. Automating the deployment sequence ensures that website updates are pushed immediately after code changes occur, resolving inconsistencies.

Can I use this to sync website content and deployment sequences triggered by code changes?▼

Yes, this handles updates for website content and deployment sequences triggered by code changes. It automatically initiates necessary scripts to update the website and notify relevant teams after modifications are made to core skills.