[ccosky]

This isn't "THE" biggest pain point, but one I dealt with today: we have new devs who ask the whole team, "Can someone do my code review?" This leads to the bystander effect: nobody volunteers to do the code review, because we all think someone else will do it. (Alternately: the team leads get asked to do every code review, because they're the leads and know the most.)

So today I wrote a Claude skill that does a git diff against master to determine what files were changed, looks at the git history of those files (most recent commits and who committed the most lines of code), filters out the people who don't work here anymore, and suggests 3 devs who could be good matches for their MR. Hopefully that will get some of the load off the team leads and staunch the "can someone do a code review for me?" requests.

So there's my suggestion to you: something that will let new devs know 1) who is the best person to do their code review and maybe even 2) who the SME for a particular area of the system is.

[lemagedurage]

I wonder if this would work even better by picking a random person of the three and pinning it on them. The bystander effect disappears completely and now there is accountability.

[ccosky]

Agreed. On a previous team I was on (no CODEOWNERS there either), we had a Python script in the build process that would look at the git history for the changed files and assign the two most likely people to the pull request automatically. I liked that a lot.

[buggy6257]

You should take a look at CODEOWNERS file specs

[ccosky]

Thank you for bringing that up! CODEOWNERS wouldn't work for us, but it might for someone else having similar struggles.