Ask HN: How to make a mono-repo AI-Ready?
The org is pushing for AI-readiness! We run a fairly large monorepo, part of that is a shared web-platform. Our team is struggling with the inbound contributions to said web-platform from other teams seeing it as the perfect code to try out their new AI-tools on. Our idea so far is that AI-Ready in this case is the same as Human-Ready. I.e. make the codebase understandable, structured, clean up any old patterns still lying around etc. With the additional of adding ClAUDE.md files describing correct patterns. However, besides the "regular", look at shit and clean it, is there any tools, or smarter ways to make our codebase easier for other to contribute to given the new tools avaialable? 1 comments on Hacker News.
The org is pushing for AI-readiness! We run a fairly large monorepo, part of that is a shared web-platform. Our team is struggling with the inbound contributions to said web-platform from other teams seeing it as the perfect code to try out their new AI-tools on. Our idea so far is that AI-Ready in this case is the same as Human-Ready. I.e. make the codebase understandable, structured, clean up any old patterns still lying around etc. With the additional of adding ClAUDE.md files describing correct patterns. However, besides the "regular", look at shit and clean it, is there any tools, or smarter ways to make our codebase easier for other to contribute to given the new tools avaialable?
The org is pushing for AI-readiness! We run a fairly large monorepo, part of that is a shared web-platform. Our team is struggling with the inbound contributions to said web-platform from other teams seeing it as the perfect code to try out their new AI-tools on. Our idea so far is that AI-Ready in this case is the same as Human-Ready. I.e. make the codebase understandable, structured, clean up any old patterns still lying around etc. With the additional of adding ClAUDE.md files describing correct patterns. However, besides the "regular", look at shit and clean it, is there any tools, or smarter ways to make our codebase easier for other to contribute to given the new tools avaialable? 1 comments on Hacker News.
The org is pushing for AI-readiness! We run a fairly large monorepo, part of that is a shared web-platform. Our team is struggling with the inbound contributions to said web-platform from other teams seeing it as the perfect code to try out their new AI-tools on. Our idea so far is that AI-Ready in this case is the same as Human-Ready. I.e. make the codebase understandable, structured, clean up any old patterns still lying around etc. With the additional of adding ClAUDE.md files describing correct patterns. However, besides the "regular", look at shit and clean it, is there any tools, or smarter ways to make our codebase easier for other to contribute to given the new tools avaialable?
Hacker News story: Ask HN: How to make a mono-repo AI-Ready?
![Hacker News story: Ask HN: How to make a mono-repo AI-Ready?]()
Reviewed by Tha Kur
on
May 20, 2026
Rating:
No comments: