Synchronize rule updates across opt-in sibling projects with dry-run proposals and confirmation.
npx skills add https://github.com/vTRKA/supervibe --skill sync-rules-vtrka
Please help me install this Agent Skill. Skill: sync-rules Source: https://github.com/vTRKA/supervibe/tree/main/skills/sync-rules Command: npx skills add https://github.com/vTRKA/supervibe --skill sync-rules-vtrka
Syncing a configuration or “rules” change across multiple sibling projects is error-prone because AI tools can overwrite local customizations or apply changes without evidence.
.supervibe/sync-config.yaml to determine which sibling projects are allowed to receive updates.Use an AI chat command like: “When I say ‘синхронизируй правила’, read the sync config, diff the updated rule against each opt-in sibling, show me the per-target dry-run changes, and only apply after I confirm.”
High-intent search queries and answers about installing and using this skill.
To propagate configuration changes safely, use an opt-in rules sync mechanism that reads a configuration file to determine allowed sibling projects. It computes dry-run diffs, detects divergent local edits, and asks whether to merge, skip, or route to manual review before applying any writes.
An evidence-first dry-run diff for rules synchronization compares source and target rule versions to show planned changes before any writes occur. This mechanism ensures you review bounded proposals and confirm them before updates are applied to sibling projects.
You synchronize rule updates by reading the `.supervibe/sync-config.yaml` file to determine which sibling projects are opt-in. The system then diffs the updated rule against each sibling, shows per-target dry-run changes, and applies the updates only after you explicitly confirm.
Yes, you can share an identical baseline rule across multi-project stacks while allowing host adapter wording to diverge. The synchronization process preserves local customizations and enforces validation, ensuring sibling projects maintain the shared baseline without losing local enforcement variations.
To ensure validation and auditability when syncing configuration updates, the synchronization process requires post-sync rule-quality validation and produces an audit log decision record per target. This enforced logging guarantees every configuration propagation event is fully traceable and verified.
kehwarDefine and configure Sync Jobs within the Frappe Tweaks framework.
redhat-copAutomate Ansible collection pull request reviews for STIG compliance.
vTRKAVerify Supervise project rules against codebases and emit rule-application reports.
OpenAuthorityCopy a file from a source path to a destination path while preserving the source.