rohanucla

7 ms·

1.
by rohanucla 3mo ago
Nice Blog!
2.
by rohanucla 3mo ago
I mean we are trying to be faster than LSPs, LSPs are a little slow for enterprise grade codebases
3.
by rohanucla 3mo ago
There is a skill.md for the agent to know about the cli, I can make update the same with more examples.
4.
by rohanucla 3mo ago
Thanks a lot Alex! for this reply, it keeps us pumped.
5.
by rohanucla 3mo ago
no setup just configures your git diff to use sem by defult, you will find the sem mcp directory on github repostiory, also there's skill.md file which will tell your agent on how to use sem.
6.
by rohanucla 3mo ago
sorry if you consider that as hijack, it was just a user's request to use this as default plugin on their git. But I will add it to let the users know thanks for the feedback
7.
by rohanucla 3mo ago
It doesn't override git diff at all, sem is its own standalone CLI. git diff continues to work exactly as before. You do sem setup only when you want to change your default git diff behavior, other wise after installing sem you can use
8.
by rohanucla 3mo ago
sem doesn't override git diff, it's a completely separate command (sem diff). Your regular git diff should work exactly as it always has after installing sem. If you want to change your git diff default behavior then you can do se
9.
by rohanucla 3mo ago
This is actually the exact scenario we just spent the last few weeks optimizing for. On a 71K-file TypeScript monorepo, sem was previously choking entirely (DNF), and now completes in 6.5s with the topology cache warm. On a 100K-file genera
10.
by rohanucla 3mo ago
Appreciate it!
11.
by rohanucla 3mo ago
That's a really compelling use case actually
12.
by rohanucla 3mo ago
Thanks! The data artifacts angle is really interesting. in some ways the problem is even harder there because data pipelines have less explicit structure than code, I guess.
13.
by rohanucla 3mo ago
haha definitely!
14.
by rohanucla 3mo ago
git is actually great, and there are not much of the issues as the world says about it, and the best is to build complimentary layers that makes it even stronger is the best bet I guess.
15.
by rohanucla 3mo ago
I am sorry, should have put up a warning there, but You can do sem unsetup, if you go to the github, you will understand more about the way to reverse it.
16.
by rohanucla 3mo ago
Lemme give you an example. when you're working in a 100K-file TypeScript monorepo and you change a utility function that parses API responses. git diff tells you that you changed n lines in that function. What it doesn't tell you
17.
by rohanucla 3mo ago
Ha, the regex approach is honestly how a lot of people start with this problem and you can get surprisingly far with it until you hit the edge cases around aliased imports, re-exports, and nested scopes where things start falling apart. Tha
18.
by rohanucla 3mo ago
This is a really interesting direction, you're essentially talking about data flow or taint analysis, where you track how a value propagates through copies and transformations rather than just following call edges. Honestly pure static
19.
by rohanucla 3mo ago
Thanks for pointing it out. I agree with you here, my testing process was quite specific to sem's output but also would love any suggestion from you of how you would design the whole testing process for this kind of tool? I can also gi
20.
by rohanucla 3mo ago
Really glad you've been using it, and yeah that's exactly the direction I've been thinking about. The line diff as the default view in code forges has always felt like an accident of history it definitely was easy to compute,
21.
by rohanucla 3mo ago
What I've been more interested in lately is structural intelligence as a field in whole. Things with LLMs break because our infra was always designed for analyzing lines(tools like grep fuzzy matching) and working on quite small sectio
22.
by rohanucla 3mo ago
It can do that, but that's a small slice of what it does. sem parses your codebase into entities (functions, classes, methods) and builds a dependency graph across files. So instead of line level analysis the whole granularity of seein
23.
Sem: New primitive for code understanding – not LSPs, but entities on top of Git(ataraxy-labs.github.io)
175 points by rohanucla 3mo ago|60 comments
24.
Opensessions – A beautiful TMUX sidebar, no nonsense(github.com)
2 points by rohanucla 3mo ago|0 comments
25.
Lazydiff – Language aware Semantic PR review TUI, way faster than lsp indexing(github.com)
3 points by rohanucla 4mo ago|0 comments
26.
by rohanucla 4mo ago
Cool project. The bidirectional source-to-AST navigation is the killer combination, clang -Xclang -ast-dump gives you a wall of text that's hard to correlate back to code, especially with C++'s implicit conversions and template in
27.
OpenSessions – real time agent tracking in tmux using hooks and process trees(github.com)
2 points by rohanucla 4mo ago|1 comments
28.
by rohanucla 4mo ago
Do lemme know about feedback and i am open to any kind of constructive criticism, it really helps me improve.
29.
Lazydiff: Terminal PR Review with AST-Aware Semantic Diff Rendering(github.com)
12 points by rohanucla 4mo ago|2 comments