Two people are asked to review 43% of all PRs
The CODEOWNERS rule for src/** names Lena and Omar. Six others have reviewed this code in the last 90 days.
hasarak looks at who reviews what, how long PRs wait, and why. Then it works on the causes: CODEOWNERS rules that send everything to two people, PRs too large to review, requests sent to people who are out.
The CODEOWNERS rule for src/** names Lena and Omar. Six others have reviewed this code in the last 90 days.
#476, #488 and #502 have waited four days. Each splits cleanly into two parts by directory.
Arman has six pending review requests and an out-of-office reply until Oct 14.
You set the goal and how it's measured. hasarak keeps reading, re-ranks what's left every week, and sends each step to the people who own that part of the system. Nothing is posted, opened or moved until someone approves it.
Breaks review wait down by repo, reviewer, PR size and time of day.
Drafts CODEOWNERS changes, reviewer rotations and PR splits.
Flags when review requests concentrate on a few people again.
Reading every PR and drafting routing changes runs on the Claude or ChatGPT accounts you connect. Add several and hasarak spreads the load.
When Claude · Work runs low, hasarak moves to ChatGPT · Acme team.
No. Findings are about routing, PR size and availability, not individual speed.
No. Reassignments and CODEOWNERS changes are drafts you approve.
From Slack status and out-of-office replies in connected Gmail accounts.
The one you connect. hasarak runs on your own Claude or ChatGPT subscription and can use several accounts at once.