Viktor.comAn AI coworker that actually does the work
Promoted
AI Risk Manager
Know what to test before merging AI-generated PRs
2 followers
Know what to test before merging AI-generated PRs
2 followers
A PR-native release-risk assistant for engineering and QA teams. It scans risky changed areas and writes a short test-first merge triage report before you ship.
Hey Product Hunt,
I built AI Risk Manager to help answer one practical question before merging a PR:
What should we test first?
It’s an open-source CLI that scans a repository or PR branch and creates a short release-risk triage report with:
- risky changed areas
- test-first actions
- merge decision: ready, review_required, or block_recommended
It runs in deterministic mode by default, so no repository code needs to be sent to an LLM. AI enrichment is optional. It works best today for backend-heavy FastAPI, Django/DRF, and Express/Node repos.
This is an open alpha. I’d love feedback from engineers and QA leads on what feels useful, noisy, or missing.
Thanks for checking it out.
I’m looking for 5 backend/QA teams to run this on one real PR.
The question: did the top 3 findings change what you would test before merge?