Skip to content
If you are an agent, a clean markdown version is at /community.md
Home
§ — · Community

Voices from the field.

Notes, reactions, and quiet approvals from practitioners using sem, weave, and the rest of the stack in anger.

§ 01 · on sem

sem

Semantic version control. Entity-level diffs, blame, and impact analysis on top of git.

17 voices

すごく良さそう!AI以前もほぼ無意識にこの程度のレビューで十分だと思ってたけど、今はなおさらだと思う
jackchuka@jackchuka
source ↗
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
source ↗
いいね、振り切ってる。Every tool in software development was designed for human hands. We're done building for human hands.
Mako@fulore
source ↗
構文解釈したgit代替commandかな。sem diffを実行すると対象ファイルの言語構文を解釈した上で差分がある関数名を提示してくれたり。diff以外にblame, graph, impactなどが用意されてる。
matsuu@matsuu
source ↗
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
source ↗
Not exactly what you asked for but you really really really gotta check this one out. Semantic diffs
merlin@merlindru
source ↗
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
source ↗
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
source ↗
Another really cool one built on top of a different abstraction from the same team
Oliver Beavers@oliverbeavers
source ↗
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
source ↗
Okay, I took a look. This is freaking awesome.
Lacy@lacybuilds
source ↗
Crazy no one ever thought about building this before. Insanely useful!
Parth S.@savss624
source ↗
This is some cool shit
Allison@allisonology
source ↗
I've wished for something like this
tmuxvim@tmuxvim
source ↗
very satisfying watching agents make changes in real time with change impact scoring courtesy of Ataraxy Labs sem-core
Charles Smart@CharlesMSmart
source ↗
Currently using @codeaborbit for the code review side and sem from Ataraxy for understanding structural impact of changes. Both are fantastic.
coderabbi@coderabbi
source ↗
良さそう、試してみよ
y_uucu@y_uucu
source ↗
§ 02 · on weave

weave

Entity-aware merges. Resolves conflicts git can't see past.

1 voice

§ 03 · on inspect

inspect

Semantic code review. Entity graphs plus LLMs reading for meaning, not syntax.

3 voices

§ 04 · on opensessions

opensessions

A tmux sidebar for managing coding-agent sessions.

3 voices

§ 04·Community|0%We are Alive