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. The approach changed a lot along the way - early versions of the secret detector flagged way too much (matching on variable names like "cache_key" instead of actual secret values), so I ended up building a whole fixture test suite just to keep false positives in check while still catching real leaks. 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. GitHub: https://github.com/neracu/rebrief

Rebrief

Turn any repo into a clean handoff dossier in 30s

Turn any repo into a clean handoff dossier in 30s