Show HN: AI Code Rating – a 3-character disclosure of how AI was used in a repo

Re:Show HN: AI Code Rating – a 3-character disclosure of how... by phillennium on Wednesday November 11, 2026 @10:12AM (#50454382)

I get the idea, the ability to understand things like that at a glance would be helpful.

But I think that at first this might create even more confusion, since people won't be able to read it "at a glance" when they meet it first time, they would need to understand "what that even is", and that creates friction and stops adoption.

So I think for such an idea to take off, it must be as immediately obvious as possible. "A2b" is not. Maybe the answer is something like "use only text descriptions that are easily understandable, but also code their values with font colors, so when a person familiar with the rating system opens yet another repository, they can quickly understand the content without reading, just by seeing three font colors".

[ Parent | on HN ]

Re:Show HN: AI Code Rating – a 3-character disclosure of how... by gregdotca on Wednesday November 11, 2026 @10:20AM (#50454483)

Thanks for the comment! And I completely agree about a rating like A2b not meaning much the first time you see it. One of the things that goes through my head is a scenario at work where the org doesn't want to use completely vibe-coded apps. With an ACR, the company could set a minimum for each part, like "Oversight b or better" or "no more than 2 for AI Share", and then it would be easy to approve or deny repos based on a quick look at their rating.

The ACR.md file itself has the rating and a quick writeup on how AI was used, but now I'm wondering if setting up something like aicoderating.com/A2b to see that specific rating explained would be helpful.

I actually thought about other ways to differentiate this (eg. colour), but if it's not plain text it will make it hard to use in certain places, and it could also cause accessibility issues.

[ Parent | on HN ]