traiproject

Content-based JSON schema routing for YAML LSP (Neovim/Helix/Emacs)

46
1
100% credibility
Found Feb 21, 2026 at 14 stars 3x -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Go
AI Summary

A lightweight proxy that sits between text editors and YAML helpers to automatically detect file types and provide precise validation rules without manual setup.

How It Works

1
😩 Frustrated YAML Editing

You're working on config files in your text editor, but suggestions are wrong or missing, making mistakes easy.

2
🔍 Discover the Fix

You find a handy tool that automatically picks the perfect rules for each file based on what it sees inside.

3
📥 Quick Install

Run a simple one-line command, and it downloads and places the tool right where your computer can find it.

4
⚙️ Switch in Editor

Update one easy setting in your editor to use this smart helper instead of the basic one.

5
📄 Open a File

Open any config file, and the tool quietly reads it to understand exactly what type it is.

6
Magic Suggestions Appear

Instantly get spot-on autocomplete, error spotting, and helpful tips without cluttering your files.

🎉 Smooth Editing Bliss

Now every YAML file works perfectly with fast, accurate help, even offline after the first use.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 14 to 46 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is yaml-schema-router?

yaml-schema-router is a Go proxy for the yaml-language-server that provides content-based JSON schema routing for YAML files in LSP editors like Neovim, Helix, and Emacs. It solves the pain of inaccurate validation and autocomplete outside VSCode, where file extensions or globs fail, by sniffing file content and directory context to dynamically assign the right schema—think Kubernetes manifests or GitHub workflows—without manual modelines. Users get precise hover, completion, and validation with zero config, plus offline support via local caching.

Why is it gaining traction?

Unlike static glob matching, it uses content-based filtering to route schemas accurately, akin to a content-based recommendation system for YAML types on GitHub, handling standard K8s resources and CRDs seamlessly. Editors forward LSP traffic through the proxy's stdio interface, injecting schemas on open/change events with minimal latency, and it respects manual overrides. The install scripts for macOS/Linux/Windows and Go builds make setup trivial.

Who should use this?

DevOps engineers writing Kubernetes YAML in Neovim or Helix, where yaml-language-server chokes on schema conflicts. GitHub Actions users tired of generic validation in Emacs. Any developer in YAML-heavy workflows needing content-based schema routing without VSCode lock-in.

Verdict

Try it if you match the use cases—solid docs and CI make it easy to test, despite 11 stars and 1.0% credibility signaling early maturity. Production use waits for config files and broader detectors.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.