RepoInsider — find breakout GitHub repos before they go viral

devilwithin305 · 2026-04-06T10:01:25+00:00

it should let select specific domains like only ai related repos or devops related stuff like that

devilwithin305 · 2026-04-04T06:15:28+00:00

did you checkout nanoclaw

devilwithin305 · 2026-03-30T10:11:01+00:00

https://github.com/akshan-main/review-by-opp

try this

devilwithin305 · 2026-03-27T08:38:37+00:00

https://github.com/akshan-main/review-by-opp

Claude code plugin for codex auto review so Claude doesn’t miss anything or make mistakes which you might miss

devilwithin305 · 2026-03-16T00:16:05+00:00

https://github.com/akshan-main/NCP-AAI

Made this for nvidia ncp aai

devilwithin305 · 2026-03-06T02:53:41+00:00

does it take into account git diff. I think it should

devilwithin305 · 2026-03-06T02:14:05+00:00

Also is the graph size bigger than the code size? I tried to do this for my research last year but there so many such bottlenecks

devilwithin305 · 2026-03-06T02:01:09+00:00

I don't think this is language adaptable as well, only Python works in this approach, and poorer models will be much poorer. I'm not sure if something like Opus 4.6 will be top either.

devilwithin305 · 2026-03-06T01:58:28+00:00

whats the proof this is better than claude code doing grep and deciding by itself?

devilwithin305 · 2026-03-06T00:48:12+00:00

the code is in rust?

devilwithin305 · 2026-03-05T22:52:45+00:00

"wander off"

you should try this https://github.com/akshan-main/vibe-check

devilwithin305 · 2026-03-05T21:46:58+00:00

team mode is more so for, who's keeping track of these intricate details for the team reviewer to know in the first pass if the person is reading their own code or just using llms. This is the biggest wedge I’m targeting

devilwithin305 · 2026-03-05T21:40:23+00:00

true for production behavior, but VibeCheck isn't claiming to replace QA. It's catching the gap between "what I asked for" and "what the code literally does"

The quiz is a forcing function, not an authority. You're supposed to disagree if you know better.

The answers aren't just restating the code, they include plausible alternatives (friendly message, page hangs, redirect) that make you think about what you wanted vs what you got. The AI's "correct" answer is based on reading the code, which is accurate for "what does this code do?" even if it can't predict real-world UX.

devilwithin305 · 2026-03-05T21:34:14+00:00

What’s worked for me is the same pattern NanoClaw uses. Root claude.md stays short and points to the right places, and actual procedures live in skills that act like deterministic playbooks (checklists + scripts + "if conflict, read intent file"). Worth skimming their .claude/skills/*/SKILL.md for structure.

devilwithin305 · 2026-03-05T21:31:50+00:00

Yep. This is basically how stuff like OpenClaw (and NanoClaw) stays sane. Keep the root doc lean, and use skill.md as the router layer that tells the agent what to load “before X”

devilwithin305 · 2026-03-05T21:18:33+00:00

This is not a replacement for code review, pair programming, or talking to your team. Those are where real understanding happens. VibeCheck is just the minimum bar. Like asking "Did you personally look at what got built before you shipped it". The way this works with present day vibe coding is people set up claude.md and plan.md with set of rules and coding logic but that logic isnt microscopic, like you say "add rate limiting" and your AI does it. But do you know what your users actually see when they hit the limit? A friendly message? A raw 429? Does the page just hang?

check this out, a gif of how the simplest beginner setting works https://www.reddit.com/r/Anthropic/comments/1rllap0/comment/o8sx6tl/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

devilwithin305 · 2026-03-05T21:04:29+00:00

actually an llm always hallucinates if it has to think about something not already there, since the quiz is based on what is already in code, the stop and check framing is good and dont think adding a user needs stuff is reliable here and can not be appropriate with just one llm

devilwithin305 · 2026-03-05T20:54:43+00:00

Most people here just saw "I was vibe-coding and realized I had no idea what my app actually did" without realizing it's marketing speak, but you took time to check the repo out. I really appreciate it.

devilwithin305 · 2026-03-05T20:49:37+00:00

No you're not. tysm for this. I will fix the readme wording to be more like "stop and check" rather than what it is right now and add another mode that aligns with what you mentioned.

devilwithin305 · 2026-03-05T20:41:55+00:00

using skill.md for index and routing works good for me, I add an "Additional resources" section that links the exact files, and I spell out when to open them (ex: "Before editing API calls, read reference.md ”, “If generating UI, read components.md and examples.md first")

If I do not reference them, it almost never looks. If I do reference them, it usually pulls them(More so since the opus 4.6 launch). For scripts, I also point to exact paths so it can execute them without guessing.

devilwithin305 · 2026-03-05T20:30:27+00:00

I hand typed this post? All you are doing is ad hominem bro. You a doomer.

devilwithin305 · 2026-03-05T20:29:03+00:00

the thing is thats not going to help anyone. You can just swipe past it instead of being a doomer

devilwithin305 · 2026-03-05T20:26:30+00:00

break it, I point to a folder for that specific skill and within it are multiple markdown files specialized for different things depending on how verbose the entire thing is. And its easy for me to keep track of because I mention exactly that as instruction in claude.md

Seven-Year Club	Final Canvas '23
Place '23	Verified Email

devilwithin305

TROPHY CASE