debug-sync

Audit WPF and HTML chip implementations for synchronization bugs.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/billwanggithub/GmtTestToolV1 --skill debug-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-sync
Source: https://github.com/billwanggithub/GmtTestToolV1/tree/main/.agent/skills/debug-sync
Command: npx skills add https://github.com/billwanggithub/GmtTestToolV1 --skill debug-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and fix synchronization bugs between WPF UI elements and their corresponding HTML representations, preventing issues like data lag, missing updates, or infinite loops.

Core Features & Use Cases

  • JavaScript Audit: Checks for common JavaScript pitfalls like missing isSyncing flags, incorrect loop conditions, and inefficient DOM manipulation.
  • WPF Audit: Verifies WPF ViewModel logic for correct state broadcasting, including checks for reference comparison bugs and proper throttling of updates.
  • Use Case: When a specific chip's interface in the web view is not updating correctly or shows stale data, use this skill to pinpoint the root cause in either the JavaScript or WPF code.

Quick Start

Run the debug-sync skill on the M8322CA chip to audit its synchronization logic.

Frequently Asked Questions about debug-sync

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

FAQPage Schema
How do I debug WPF and HTML synchronization issues causing stale data?

To debug WPF and HTML synchronization issues, audit JavaScript for missing `isSyncing` flags and infinite loops, then verify WPF ViewModel state broadcasting and throttling to pinpoint data lag or missing updates.

Why does my web view JavaScript loop infinitely during UI updates?

Infinite loops during web view UI updates typically occur from missing `isSyncing` flags and incorrect loop conditions in JavaScript, requiring an audit of DOM manipulation and mapping logic to prevent recursive synchronization.

How can I check WPF ViewModel logic for incorrect state broadcasting?

Check WPF ViewModel state broadcasting by analyzing `ViewModels/<Chip>ViewModel.cs` files to identify reference comparison bugs and verify proper throttling of update notifications sent to the HTML interface.

What files do I need to fix WPF and HTML data mapping problems?

Fixing WPF and HTML data mapping problems requires analyzing `wwwroot/<chip>_interface.js` and `ViewModels/<Chip>ViewModel.cs` files to audit JavaScript mapping logic and WPF ViewModel state broadcasting.

Does this synchronization audit work for any specific chip implementation?

Yes, the synchronization audit targets specific chip implementations, analyzing the corresponding interface JavaScript and WPF ViewModel files to diagnose synchronization bugs like data lag or missing updates for that specific chip.