WeSearch

Overllm – flags where you're paying an LLM to do a regex's job

·5 min read · 0 reactions · 0 comments · 6 views
Overllm – flags where you're paying an LLM to do a regex's job

Catch the LLM/AI calls you didn't need. A fast, deterministic linter that flags LLM API calls where plain code is simpler, cheaper, and more reliable. Your GPT call is a regex. - theadamdaniels...

Original article
GitHub
Read full at GitHub →
Opening excerpt (first ~120 words) tap to expand

overllm Catch the LLM/AI calls you didn't need. overllm is a small, fast linter with one job: find the places in your code where you call an AI model to do something plain code does better. You called GPT to parse a date. You called a model to extract JSON that json.loads already handles. You are paying latency, money, and nondeterminism for a regex. It reads your code with a real parser: Python through the standard-library ast, and JavaScript and TypeScript through tree-sitter. No model runs, no network, no API key. Same code in, same result out. Fast enough for a pre-commit hook. Everyone else lints the code the AI wrote. overllm catches where you are paying an AI to do what a library already does.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub