Neracu's profile on Product Hunt

About

Full-stack dev & automation enthusiast. Building open-source tools to make developers' lives a bit easier.

Links

GitHub

Badges

Tastemaker

Gone streaking 10

Gone streaking

Gone streaking 25

View all badges

Maker History

VastSee what breaks before you ship AI-generated code
Aug 2026
RebriefTurn any repo into a clean handoff dossier in 30s
Jul 2026

🎉

Joined Product HuntApril 13th, 2026

Forums

•

1mo ago

Vast - See what breaks before you ship AI-generated code

Vast connects to your GitHub repo and shows what a code change actually breaks - before you commit it. Click a file, see dependencies, cycles, god services, overloaded modules. Built on tree-sitter, so it reads real imports, not just folder structure. Made for teams shipping AI-generated code (Cursor, Copilot, Claude etc.) who need to know the blast radius before merging. Source code is never stored - only the dependency graph. Free tier + early-bird Pro pricing.

•

2mo ago

AI writes fast, but do you know what it's breaking?

Been shipping a lot of code lately with Cursor/Claude doing a good chunk of the actual writing. Velocity is great, but I've noticed I trust my own understanding of the codebase less than I used to - I'll touch one file and have no real sense of what else depends on it until CI (or prod) tells me.

Ended up manually tracing imports before merging anything non-trivial, just to make sure I'm not breaking something three files away.

Anyone else running into this, especially with AI-assisted code? Curious if it's a real pattern or just me being paranoid.

•

2mo ago

Turn any repo into a clean handoff dossier in 30s

Hey Product Hunt!

I built rebrief after losing days more than once to reverse-engineering someone else's codebase (including my own vibe-coded ones) - figuring out the stack, hunting for stray TODOs, wondering if a secret got left in somewhere.

rebrief scan . - and in about 30 seconds you get a REBRIEF.md: stack, a filtered history of real decisions, a risk map, and a checklist of where to start. Fully local, free, open source.

Genuinely curious: what other signals would you want in a report like this? Already thinking about a .rebriefignore file and a GitHub Action for auto-scanning PRs.