Validate code edits against diagnostics before applying them.
npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-safe-edit
Please help me install this Agent Skill. Skill: lsp-safe-edit Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-safe-edit Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-safe-edit
Wraps code edits with a before/after diagnostic comparison to catch regressions before touching disk. Speculatively previews the change (simulate_edit_atomic), then surfaces code actions for quick fixes if post-edit diagnostics reveal issues.
Open the target file(s), preview the change with simulate_edit_atomic, and apply the edit only if the diagnostic delta is acceptable.
High-intent search queries and answers about installing and using this skill.
Validating code edits against live diagnostics requires speculatively previewing the change to measure the error delta before writing to disk. This before/after diagnostic comparison catches regressions early by surfacing post-edit issues without modifying files.
Multi-file refactors can be previewed for diagnostic regressions using speculative chain simulations. This coordinates edits across the workspace, measuring the diagnostic delta before applying changes to ensure no new errors are introduced.
A speculative edit preview in LSP refactoring simulates an atomic code change to measure the diagnostic error delta before touching disk. It wraps edits with before/after diagnostic comparisons to catch regressions and surfaces code actions for quick fixes.
Checking code diagnostics for refactoring requires an active agent-lsp server along with LSP tools for opening documents and retrieving diagnostics. These dependencies are necessary to validate edits, generate speculative previews, and apply formatting checks.
Code actions help fix post-edit diagnostics by surfacing quick fixes after a speculative edit preview reveals issues. When the diagnostic delta shows new errors, code actions provide automated resolutions to ensure a clean refactoring result before applying.
Safely applying incremental bug fixes without regressions is best done by simulating the edit atomically, checking the diagnostic delta, and applying only if the error count is acceptable. Post-edit formatting checks and code actions ensure a clean result.
blackwell-systemsAnalyze source files to list symbols, highlight usages, and retrieve type info.
HmbownApply a single coordinated change across an entire row or pipeline.
rkumar261Simulate user interactions, identify defects, and apply atomic fixes with re-verification.
binfen1Monitor live apps for console errors, performance regressions, and page failures.
