Debug LiteSuite Electron webview, preload, IPC, and bridge layers with disk logging and live monitoring.
npx skills add https://github.com/ahostbr/liteharness --skill ls-debug
Please help me install this Agent Skill. Skill: ls-debug Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-debug Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-debug
ls-debug helps you stop guessing when LiteSuite’s Electron webview, preload, IPC, or bridging fails, by setting up persistent disk logging and a focused monitor so you can see exactly where the runtime breaks.
Trigger the LiteSuite flow and use ls-debug to set up a component disk logger, tail the log while reproducing the issue, then fix the specific failure point revealed by the monitor output.
High-intent search queries and answers about installing and using this skill.
To debug a blank Electron webview, you need persistent disk logging and live monitoring to capture runtime evidence. Add structured boundary logs at handoffs, forward webview console output to disk, and trap renderer errors early in the wrapper HTML to trace failures.
An Electron preload bridge silently fails when IPC messages or initialization events are missing. You can identify the exact failure point by adding boundary visibility logs and using a filtered monitor to tail disk-persistent debug files while reproducing the issue.
The best way to monitor IPC handshake timeouts is using a monitor-driven debugging loop with filtered tail commands. This watches for missing preload exposures and non-firing events during rebuild and launch, revealing exactly where the runtime breaks.
To capture Electron renderer errors before the webview loads, trap renderer errors early in the wrapper HTML. Forward webview console messages through the preload layer to disk-backed log files so failures become traceable across runs.
Yes, disk-persistent logging fixes stuck spinners in Electron webviews by preserving runtime evidence across runs. Component-specific debug log files under your home directory capture spawn failures and missing handshake events for a read-fix-repeat iteration.
gouravsingh311Orchestrate Electron IPC communication between main and renderer processes.
jMertaDiagnose and patch failing GitHub Actions CI workflows using the GitHub CLI.
sblueminAutomate end-to-end testing of the Fleet Console Electron Desktop shell.
BifrasDiagnose Electron and React apps via console capture, IPC tracing, and state inspection.
