What changes in code review, testing and governance when agents write most of the code. Field notes, verified tool comparisons and what teams publish about their own review load.
Maintained by Kodus. That is stated in the footer of every page and on /about.
Part of a small network of sites run by the same team, each with its own editorial line: aicodereview.io for the AI code review category and codereviewbench.com for the model benchmark.
Astro 5 with Tailwind, deployed on Vercel. Pages are prerendered to static HTML on the CDN; only /api/* runs on demand as a serverless function.
Built from the same codebase as aicodereview.io. Everything that makes this site this site lives in src/site.config.ts: domain, name, description, nav, analytics id and who maintains it. A new site in the network copies the repo and edits that one file.
src/content/blog/*.mdx— posts. Categories arebest-of,alternatives,comparison,guide,explainer,review.src/content/tools/*.json— the tool directory. Pricing, license, self-hosting, platform support and alastVerifieddate on every entry. Shared across the network, so a correction here should be carried to the sibling repos.
Every factual claim about a vendor is read from that vendor's own public pages and stamped with the date. When it cannot be confirmed from a primary source the field says unknown.
Posts arrive through the content API rather than by hand. See CONTENT-API.md. In production an accepted post becomes a commit to this repo, which triggers the deploy and rebuilds the static site.
npm install
npm run devCONTENT_API_KEY=test npm run dev if you want to POST to /api/posts locally.