Community voices

Inspect does semantic code review using entity graphs + LLMs – it understands what your code *means*, not just what it says. Most linters catch syntax. This catches logic.

Gustavo Salami@gustavosalami
inspect

annotation-led review is the future. I wonder if you'd consider incorporating something like Inspect

Oliver Beavers@oliverbeavers
inspect

すごく良さそう!AI以前もほぼ無意識にこの程度のレビューで十分だと思ってたけど、今はなおさらだと思う

jackchuka@jackchuka
sem

If you use tmux daily and have recently been using coding agents, this project might be worth checking out. A tmux sidebar that can synchronize and manage the status and sessions of different coding agents.

Jintao Zhang@aiandcloud
opensessions

I just gave opensessions a spin after vibe-slopping my own solution – amazing work

Nimrod Gutman@theguti
opensessions

Tried cmux/conductor/superset/etc, the random bugs are really annoying. I've completely abandoned them for tmux plugins. Using opensessions.

Micro 小熊猫@xxm459259
opensessions

Remember Weave, the entity-level git merge tool? Same team just shipped Sem: semantic version control on Git. Instead of 'line 43 changed' you get 'function validateToken added.' Entity-level diffs, blame, impact analysis. 16 langs via tree-sitter.

Zoltan@zoltansoon
sem

いいね、振り切ってる。Every tool in software development was designed for human hands. We're done building for human hands.

Mako@fulore
sem

構文解釈したgit代替commandかな。sem diffを実行すると対象ファイルの言語構文を解釈した上で差分がある関数名を提示してくれたり。diff以外にblame, graph, impactなどが用意されてる。

matsuu@matsuu
sem

you need to check this out. this has SO many applications, from build optimizations to CI / CD, to LLMs. i have no doubt that this, or a project like it, will become the go-to in the future

merlin@merlindru
sem

Not exactly what you asked for but you really really really gotta check this one out. Semantic diffs

merlin@merlindru
sem

git tells you 'line 43 changed'. sem tells you 'function validateToken was added in src/auth.ts'. entity-level diffs on top of git. also does impact analysis, dependency graphs, and entity-level blame. this is how code review should work

Anandu@BFRAnandu13
sem

Git diff está oficialmente muerto. En vez de escupirte 300 líneas para que adivines qué cambió... te dice la verdad: Función login() fue modificada. Clase UserService renombrada. Método validateToken() se movió.

Erick@ErickSky
sem

Another really cool one built on top of a different abstraction from the same team

Oliver Beavers@oliverbeavers
sem

if i never had to write 'this code hasn't changed, i just moved it' comments on my own prs again i'd be a happy bunny

jenna@jjenzz
sem

Okay, I took a look. This is freaking awesome.

Lacy@lacybuilds
sem

Crazy no one ever thought about building this before. Insanely useful!

Parth S.@savss624
sem

This is some cool shit

Allison@allisonology
sem

I've wished for something like this

tmuxvim@tmuxvim
sem
← Back