Disclaimer
Disclaimer: due to unforeseen circumstances we have to leave before noon, so we cannot be there for the demos and pitches.
Core trick
Matches YAML rules as tree-sitter queries or regexes, and serves the results over LSP so editors and agents fix violations.
Description
Disclaimer: due to unforeseen circumstances we have to leave before noon, so we cannot be there for the demos and pitches. That said, we had a lot of fun building it.
Lintropy is a Rust-based linter and LSP server that lets you define
repo-specific rules in YAML. It uses tree-sitter queries for structural
matching and regex for text matching, so you can enforce conventions
that generic linters like ESLint or Clippy can't, such as "API handlers
must live under src/api/" or ".unwrap() is banned outside tests".
Rules are enforced everywhere: CLI, CI, editors (VS Code, Cursor,
JetBrains), and coding agents ( Codex, Claude Code), which matters as
agents generate more code and convention drift outpaces review bandwidth.
A bundled SKILL.md teaches agents the rule schema, so they can both
author new rules from plain-English descriptions and fix their own
violations in a write → lint → fix loop via the LSP.
README excerpt
<div align="center"> <img src="logo.png" alt="Lintropy logo" width="220" /> # Lintropy **Repo-native linting for architecture, boundaries, and team-specific rules.** [](https://github.com/Typiqally/lintropy/actions/workflows/ci.yaml) [](https://github.com/Typiqally/lintropy/releases) [](https://www.rust-lang.org/) [](LICENSE) [](#built-for-agent-workflows) [](#how-it-works) [](#how-it-works) </div> --- Lintropy is a linter for rules your repo actually cares about. It started at [The IDE Reimagined: JetBrains Codex Hackathon](https://cerebralvalley.ai/e/jetbrains-x-openai-hack), a two-day San Francisco event focused on building AI-powered developer tools alongside JetBrains and OpenAI engineers. > [!WARNING] > This project began as hackathon code and is not actively maintained right > now. Expect rough edges, incomplete features, and bugs before using it in > production workflows. Most linters ship a fixed catalog. Lintropy does the opposite: rules live in your repo, one YAML file at a time, de