𝐈’𝐦 𝐨𝐟𝐟𝐢𝐜𝐢𝐚𝐥𝐥𝐲 𝐨𝐩𝐞𝐧-𝐬𝐨𝐮𝐫𝐜𝐢𝐧𝐠 𝐎𝐧𝐛𝐨𝐚𝐫𝐝-𝐂𝐋𝐈!

Animesh Yadav — Sat, 04 Jul 2026 13:33:24 +0000

𝐎𝐧𝐛𝐨𝐚𝐫𝐝-𝐂𝐋𝐈 𝐢𝐬 𝐚 𝐥𝐨𝐜𝐚𝐥-𝐟𝐢𝐫𝐬𝐭, 𝐬𝐭𝐚𝐧𝐝𝐚𝐥𝐨𝐧𝐞 𝐭𝐨𝐨𝐥 designed to enforce architectural boundaries and map system dependencies directly in your terminal, blocking bad code long before it ever hits a PR review.

Check out the repository, drop a ⭐ to support the launch, and view the contribution guidelines here:
Website Link:

Calling all open-source developers, backend engineers, and systems enthusiasts:
The project is officially open to the community, and I am looking for contributors to help scale it. Whether you want to optimize the Go concurrency models, expand Tree-sitter support for more languages, or test the limits of the parsing engine, I would love your feedback and code.

Let’s build a high-performance standard for code architecture together.

How I built a Go CLI to parse 50k files in <10s and stop architectural drift

Animesh Yadav — Fri, 03 Jul 2026 14:58:49 +0000

You know the feeling. You jump into a massive, legacy monorepo, and instead of writing code, you spend two weeks trying to figure out which microservice talks to what. The original architecture is either lost to "spaghetti dependencies" or hidden in an outdated Confluence document.

I wanted a tool to automatically enforce boundaries and map this out. The problem? Existing tools were either painfully slow (relying on regex) or used LLMs that hallucinated system relationships. I needed something blazing fast and 100% deterministic. So, I built Onboard-CLI.

What is Onboard-CLI?
Onboard-CLI is a local-first, standalone binary that maps your codebase's architecture and blocks dependencies that violate your established boundaries—before they ever hit a PR review.

You can check out the source code and try it locally:

The Tech Stack (and why I chose it)

Go for Concurrency
I needed raw speed. Go’s concurrent worker pools allowed me to engineer the CLI to rip through massive codebases—analyzing over 50,000 files in under 10 seconds.
Tree-sitter for AST Parsing
I completely avoided AI and regex. Instead, Onboard-CLI uses Tree-sitter to parse the Abstract Syntax Tree (AST) of the code. This means it maps the actual structural dependencies with 100% accuracy without ever executing the code.

How it works in practice
The workflow is designed to be completely invisible until you make a mistake:

Define: You define your architectural rules in a simple architecture.yaml file (e.g., "The UI component cannot directly call the Database layer").

Hook: The CLI runs as a local Git hook.

Enforce: If you try to commit code that violates the YAML rules, the CLI blocks the commit and shows you exactly where the architectural drift occurred.

Because it's a standalone binary, your proprietary code never leaves your local machine.

I need your feedback!
I am actively looking to break this tool and find its limits. Since I'm transitioning into the industry soon, getting real-world edge cases from senior engineers is incredibly valuable to me.

How does your team currently handle architectural decay?

Have you run into specific edge cases with Tree-sitter parsing?

DEV Community: Animesh Yadav

𝐈’𝐦 𝐨𝐟𝐟𝐢𝐜𝐢𝐚𝐥𝐥𝐲 𝐨𝐩𝐞𝐧-𝐬𝐨𝐮𝐫𝐜𝐢𝐧𝐠 𝐎𝐧𝐛𝐨𝐚𝐫𝐝-𝐂𝐋𝐈!

How I built a Go CLI to parse 50k files in <10s and stop architectural drift