lsp-chat-recovery-loop

To debug flaky Remora LSP chat delivery failures, this Skill applies an end-to-end recovery workflow that transforms scattered raw logs into a concise, testable hypothesis report alongside a minimal code fix and verification steps.

The best way to turn raw logs into a testable fix hypothesis is to process them through a structured recovery loop that identifies reliability regressions and records exact origins for evidence, outputting a run directory and simplified logs for reproducible testing.

You generate a minimal code fix from e2e scenario logs by applying the recovery workflow, which acts on deterministic logs to hypothesize fixes, produce a run directory, and provide clear verification steps for handoff and reproducible testing.

Yes, this workflow supports reproducible testing of LSP reliability regressions by acting on deterministic logs, generating a run directory with simplified logs, and recording exact origins to ensure evidence-based verification.

No specific dependencies are required to analyze e2e logs, as the diagnostic loop operates independently using scripts and references to process raw logs and generate actionable hypothesis reports for Remora LSP chat delivery.

Remora LSP chat delivery regressions need simplified logs because scattered raw logs obscure the root cause, and simplifying them into a structured run directory enables faster diagnosis and reproducible minimal code fix generation.