automerge-swift-diag

Diagnose Automerge Swift runtime errors with symptom-based fixes.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/sitapix/automerge-swift-skills --skill automerge-swift-diag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: automerge-swift-diag
Source: https://github.com/sitapix/automerge-swift-skills/tree/main/skills/automerge-swift-diag
Command: npx skills add https://github.com/sitapix/automerge-swift-skills --skill automerge-swift-diag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides symptom-based troubleshooting and guidance for Automerge Swift runtime errors, including decode failures, binding crashes, sync issues, and merge-related problems, helping developers quickly identify causes and apply fixes.

Core Features & Use Cases

  • Symptom-based diagnostic guides for common Automerge Swift errors (DocError, LoadError, CodingKeyLookupError, PathParseError, BindingError, DecodeSyncStateError, ReceiveSyncError, ScalarValueConversionError, Merge Problems, and Precision Issues).
  • Practical fixes, common causes, and example code snippets to resolve runtime problems and improve stability after merges.
  • Structured references and in-depth sections to inspect, reason about, and recover from synchronization and schema drift problems in Automerge Swift.

Quick Start

Read error messages, locate the matching troubleshooting section, and follow the prescribed fixes to stabilize the Automerge Swift runtime in your project.

Frequently Asked Questions about automerge-swift-diag

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

FAQPage Schema
How do I fix Automerge Swift runtime errors like DocError or LoadError?

Automerge Swift sync errors are diagnosed by inspecting sync state validation and checking for schema drift between peers. Structured troubleshooting guides help trace ReceiveSyncError and DecodeSyncStateError causes, offering practical steps to verify sync state consistency and recover failed synchronization sessions.

Why does my Automerge Swift app crash with CodingKeyLookupError or PathParseError?

Automerge Swift crashes with CodingKeyLookupError or PathParseError occur when binding paths fail to resolve against the document schema. Diagnosing these binding issues involves verifying coding key mappings, validating path strings, and applying guardrails to ensure schema and binding path alignment before runtime access.

How do I resolve merge problems and data precision issues in Automerge Swift?

Merge problems and precision issues in Automerge Swift are resolved by inspecting conflicting document states and validating scalar value conversions. Diagnostic procedures provide code snippets to handle ScalarValueConversionError, verify merge state integrity, and implement validation steps that prevent data loss during synchronization.

Does Automerge Swift troubleshooting support schema drift recovery?

Automerge Swift troubleshooting supports schema drift recovery through in-depth sections that help inspect, reason about, and restore document consistency. You can use structured references to identify schema mismatches across peers and apply guided validation steps to recover from synchronization failures caused by drift.