Patchmark – LSP for reviewing code changes/diffs in text
LSP for diffs inside Markdown solves a specific AI-review pain point no one else targets.
Write Language Servers that comply with 3.17 of the LSP Specification
Up-to-date LSP 3.17 support in Go beats outdated alternatives like sourcegraph/go-lsp.
Go developers building IDE extensions, language tools, or static analysis servers.
tliron/glsp · sourcegraph/go-lsp · nanobox-io/golang-lsp
LSP for diffs inside Markdown solves a specific AI-review pain point no one else targets.
Turns fuzzy AI prompts into a lightweight contract: SIGNATURE, BEHAVIOR (WHEN/THEN) and TESTS can be written as .rune YAML or embedded Markdown, letting any model or language generate the same behavior. Clever, low-friction idea with practical utilities (drift detection, reverse-engineer skills), but it’s a pattern rather than a product — adoption will hinge on tooling and CI integrations to make these specs enforceable at scale.
Wires up svelte-language-server to Claude Code—useful but just configuration.
Five SQLite engines from one spec, all passing 99% of the upstream sqllogictest corpus.
Static analysis for Scheme beats REPL-based completion on broken code.
LSP for CSS variables with cascade awareness, but Stylelint, PostCSS, and editor extensions already cover this.