sync-conflict-resolver

Resolve offline-online data conflicts with a deterministic FIFO mutation queue.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/filimorniga-ux/farmacias-vallenar-suit --skill sync-conflict-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-conflict-resolver
Source: https://github.com/filimorniga-ux/farmacias-vallenar-suit/tree/main/.agent/skills/sync-strategy
Command: npx skills add https://github.com/filimorniga-ux/farmacias-vallenar-suit --skill sync-conflict-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a robust strategy to reconcile divergent offline and online states during synchronization, ensuring deterministic processing order and auditable decisions.

Core Features & Use Cases

  • Queue-Based Synchronization: offline actions enter a persistent MutationQueue and are processed FIFO to prevent out-of-order submissions.
  • Conflict Resolution Rules: inventory stock checks enforce business rules, price changes are tracked with price_override for auditing, and client edits are merged intelligently.
  • End-to-end applicability: works with workers, cronjobs, or any sync logic to harmonize data across client and server.

Quick Start

Integrate the sync-strategy module into your worker or cronjob setup and start the MutationQueue processing to begin resolving conflicts.

Frequently Asked Questions about sync-conflict-resolver

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

FAQPage Schema
How do I handle offline synchronization conflicts deterministically?

Offline synchronization conflicts are resolved by routing actions through a persistent MutationQueue processed in FIFO order, enforcing deterministic state reconciliation and preventing out-of-order data submissions.

What is the best way to reconcile offline and online state for inventory and pricing?

Reconcile offline and online state by applying deterministic conflict resolution rules that check inventory stock, track price changes via price_override audit flags, and intelligently merge divergent client and server data.

Does queue-driven conflict resolution work with cronjobs and background workers?

Queue-driven conflict resolution works across worker-initiated, cronjob, or sync-driven flows, applying consistent state reconciliation logic to harmonize data across client and server environments.

How do I audit offline price changes and stock updates during data synchronization?

Audit offline price changes and stock updates during data synchronization by enforcing explicit conflict handling rules that attach audit flags like price_override and stock status to mutation queue entries.

Why does offline state synchronization require a persistent mutation queue?

Offline state synchronization requires a persistent mutation queue to guarantee FIFO processing order, ensuring offline actions are submitted sequentially and preventing out-of-order conflicts when connectivity is restored.